Seasonal Search Pages Are Prepared Too Late
Observable evidence: Compare holiday-page publication and update dates with Search Console demand, inventory readiness, delivery cutoffs, internal links, and indexation. The source example begins on February 1st and uses a preparation window of 45 to 60 days. No supporting source URL establishes that window as a search requirement, so use it only as a previously published operating reference.
Consequence: If a Valentine's Day page is created after relevant demand has begun, the florist has less time to make the page useful, connect it internally, have it crawled, and let customers discover the current offer before order deadlines.
Correction: Build a 12 month merchandising and editorial calendar around actual occasions, stock, delivery capacity, photography, and offer deadlines. When a useful evergreen holiday destination already exists, maintain /valentines-day-delivery rather than creating a disposable annual page without a clear reason.
Owner: Content or SEO owner working with merchandising and delivery operations.
Verification: Confirm the live page is current, indexable, internally linked, and aligned with the offer. The source contrasts /valentines-day-2024 with /valentines-day-2023 as an example of yearly URL replacement; inspect the real site before deciding whether consolidation is appropriate.
Severity: critical
Floral Images Lack Useful Context or Efficient Delivery
Observable evidence: Crawl image assets and review alt text, filenames, captions, dimensions, file weight, surrounding product copy, and rendered context. A generic filename such as IMG_001.jpg is evidence of weak asset labeling, but not by itself proof of a ranking loss.
Consequence: Important arrangement details may be harder for search systems and assistive technologies to interpret, while unnecessarily large images can make browsing bouquets, galleries, and occasion pages slower.
Correction: Use concise descriptive alt text when an image conveys information, meaningful filenames, appropriate dimensions, compression, and surrounding copy that identifies the arrangement without stuffing search terms.
Owner: Ecommerce content owner, with frontend support for image delivery.
Verification: Re-crawl the updated templates, inspect rendered accessibility behavior, and compare transfer size and page performance before and after the change. If the portfolio contains 50 wedding photos, verify that their descriptions reflect what is actually shown rather than adding venue or service terms mechanically.
Severity: high
Public Business Details No Longer Match the Real Shop
Observable evidence: Establish the florist's current name, address, phone details, genuine locations, profile information, website contact details, and priority directory records. Distinguish harmless formatting differences from factual conflicts that could misdirect a customer.
Consequence: Wrong or stale location data can send calls, visits, or orders to incorrect details and make the business harder to reconcile across local surfaces.
Correction: Set one verified business record as the source of truth, then correct materially inaccurate profiles and directory entries. Do not treat citation uniformity as a guaranteed Map Pack ranking lever.
Owner: Local marketing or operations owner with access to official shop records.
Verification: Recheck the edited sources and customer-facing profiles after updates. The source example describes 20 directory listings and a 30 percent decline in local map views after an address change; because no supporting URL or attribution method is present, retain those figures only as a historical example rather than evidence of causation.
Severity: critical
One Generic Page Tries to Cover Every Occasion and Flower Type
Observable evidence: Map Search Console queries, internal site searches, actual inventory, delivery options, and buyer journeys for sympathy, wedding, anniversary, prom, and named flower varieties. Identify cases where a broad flower-shop page does not answer a more specific need.
Consequence: Shoppers may land on a page that does not show the products, availability, delivery context, or decision information implied by their search.
Correction: Build or improve category and occasion pages only where the florist has genuine products or useful service information. Location wording should reflect a real storefront or meaningful delivery information, not a nominal market created solely for search.
Owner: SEO and merchandising.
Verification: Confirm each destination is distinct, useful, internally linked, and supported by the current catalog. The source scenario compares a #1 position for a broad query with #50 for a funeral-flower query; use it as an illustration of intent mismatch, not an expected ranking pattern.
Severity: high
Google Business Profile Product Information Is Missing or Outdated
Observable evidence: Inspect each eligible profile and compare displayed bouquets, seasonal products, pricing, availability, and destination links with the florist's current website and merchandising records.
Consequence: A shopper evaluating the florist from the profile may receive less complete or stale product information and may need extra steps to determine what can actually be ordered.
Correction: Maintain accurate product information when the feature is available and useful. Choose an update process based on how often the assortment changes rather than claiming a required posting cadence.
Owner: Local marketing or ecommerce merchandising.
Verification: Check the public profile after edits, open destination links, and compare displayed items with the live catalog and current seasonal offer.
Severity: medium
Local Content Mentions Places Without Demonstrating Local Usefulness
Observable evidence: Review pages about venues, hospitals, funeral homes, neighborhoods, event spaces, and delivery areas. Look for genuine florist experience, logistics, photos, order guidance, delivery limitations, or other information a local customer can use.
Consequence: Repetitive city or venue pages can add little value and may leave shoppers without the practical details they expected from a local result.
Correction: Publish a dedicated local or venue page only where there is real location-specific substance. Do not imply a partnership that does not exist. The source's Top 5 Wedding Venues concept is useful only when the florist can add accurate, experience-based information rather than generic summaries.
Owner: Content owner with input from delivery, wedding, or event operations.
Verification: Fact-check named places, service statements, relationships, and delivery claims, then confirm that each page serves a distinct user need.
Severity: high
High-Resolution Photography Overloads Important Pages
Observable evidence: Test representative home, category, product, gallery, and occasion templates on mobile. Identify the largest visual assets, the LCP element, total transfer weight, rendering delays, and field performance where available. The source uses more than 3 seconds as an example threshold, but this JSON does not establish that most visitors leave at that point.
Consequence: Slow rendering can delay product discovery, image browsing, option selection, and checkout interaction on constrained connections.
Correction: Resize images for their rendered use, compress them, serve appropriate modern formats such as WebP, reserve layout space, and defer below-the-fold media where that does not delay primary content.
Owner: Frontend or performance owner with support from the team preparing floral media.
Verification: Repeat the same tests after deployment and compare the affected templates. The source example describes a 15MB homepage taking 8 seconds on a standard 4G connection; treat it as an illustrative failure case rather than a universal benchmark.
Severity: critical
