Start by proving that the florist's important pages are secure, crawlable, indexable as intended, and usable on the devices customers rely on.
LocalBusiness and Product structured data
Evidence required: rendered markup, visible shop details, visible product information, eligibility requirements, and current page content. Pass condition: the markup accurately reflects information shown to customers and contains no critical validation errors.
Fail condition: structured data introduces unsupported fields, stale product facts, or business information that conflicts with the page. Severity: high on core location and product templates. Owner: SEO and development.
Corrective action: align the markup with current visible content and remove unsupported properties. Validation: retest the deployed templates against Schema.org definitions and Google's current structured-data validation guidance. Markup can help describe eligible content, but should not be treated as a guaranteed search enhancement.
Mobile performance
Evidence required: field and lab measurements for representative home, collection, product, cart, and checkout templates. The source previously stated that over 70 percent of floral searches occur on mobile, but no supporting source URL is present, so that figure remains an historical reference requiring reconciliation.
Pass condition: the tested mobile journey has no unresolved performance defect that materially obstructs product discovery or checkout. Fail condition: oversized images, scripts, rendering delays, or layout movement repeatedly create avoidable friction.
Severity: critical for transaction templates. Owner: frontend or performance owner. Corrective action: optimize only the assets, scripts, or rendering behavior identified by the measurements. Validation: rerun the same PageSpeed Insights or equivalent tests and compare field trends after deployment.
Occasion URL structure
Evidence required: crawl export, search-intent map, category navigation, internal links, canonicals, and indexation samples for /flowers/anniversary/ and /flowers/sympathy/. Pass condition: each important occasion destination has a stable role, useful content, and consistent internal signals.
Fail condition: multiple pages compete for the same intent, important pages are orphaned, or URL changes occur without a migration reason. Severity: high. Owner: technical SEO and ecommerce development.
Corrective action: consolidate conflicting paths, improve internal navigation, and preserve useful URLs where practical. Validation: recrawl and confirm sitemap, canonical, internal-link, and indexation signals agree.
Seasonal broken links and retired pages
Evidence required: crawl data for holiday URLs, live collection destinations, redirect chains, historical internal links, and customer-facing navigation. Pass condition: active seasonal destinations resolve correctly and obsolete pages have an intentional status.
Fail condition: important links end in 404 errors, or a 301 redirect sends visitors to a destination that does not satisfy the prior intent. Severity: high near major gifting periods. Owner: SEO and development.
Corrective action: restore a useful destination, redirect only when a genuinely equivalent replacement exists, or keep a not-found response when there is no suitable substitute. Validation: recrawl the affected paths and manually confirm the destination, page purpose, and customer journey.
HTTPS and certificate health
Evidence required: protocol behavior, certificate validity, mixed-content checks, redirects, and ecommerce checkout behavior. Pass condition: customer-facing pages and checkout load securely with a valid certificate and no avoidable mixed-content errors.
Fail condition: certificate, protocol, or redirect defects interrupt browsing or payment. Severity: critical. Owner: hosting, platform, or development owner. Corrective action: repair certificate or protocol configuration and any dependent insecure resources. Validation: test with SSL Labs or comparable tooling and verify the complete purchase path.