Implement Accurate Bakery and FoodEstablishment Structured Data
Evidence required: inspect the live markup and compare business type, address, opening hours, menu references, and other properties with visible page content.
Pass condition: applicable markup is valid, current, and supported by the page. Fail condition: markup is missing where the implementation requires it, invalid, contradictory, or contains unsupported facts.
Severity: High when incorrect markup conflicts with core business information; otherwise Medium. Owner: Developer with business-fact approval from operations. Corrective action: remove unsupported properties, use the most applicable documented type, and keep markup synchronized with the visible page.
Validation: retest with current Google validation tools and manually compare rendered content with the markup. Tools: TechnicalSEO Schema Generator, Google Rich Results Test
Audit Mobile Performance on Revenue-Relevant Pages
Evidence required: test the homepage, menu, product, location, and ordering or inquiry flow on representative mobile devices and with performance diagnostics.
Pass condition: important content and actions render reliably without avoidable delay or layout breakage. Fail condition: oversized assets, blocking scripts, unstable layouts, or broken interactions materially interfere with use.
Severity: High when ordering, directions, or product discovery is impaired. Owner: Developer. Corrective action: reduce page weight, repair rendering defects, and prioritize the critical customer path. Validation: rerun diagnostics and repeat the mobile task. Tools: Google PageSpeed Insights, GTmetrix
Publish Core Menu Information in Crawlable HTML
Evidence required: verify that important cupcake flavors, dietary notes, custom-order information, and menu categories exist in the rendered page rather than only inside a PDF.
Pass condition: customers and search engines can access the core menu without downloading a file. Fail condition: essential product information is PDF-only or unusable on mobile. Severity: High for a shop whose menu is central to conversion.
Owner: Content and web team. Corrective action: publish the core information in responsive HTML while retaining a printable file if useful. Validation: inspect rendered HTML and complete the menu journey on mobile. Tools: Search Console, CMS Editor
Check HTTPS and Checkout Security Configuration
Evidence required: verify that the site loads securely, redirects consistently, and that any order flow uses the security controls required by the payment stack and provider.
Pass condition: no mixed-content warnings or broken secure flows. Fail condition: insecure resources, certificate errors, or checkout configuration problems. Severity: Critical where security or checkout is affected.
Owner: Developer or hosting administrator. Corrective action: repair certificate, redirect, and mixed-content issues. Validation: retest the customer path and server configuration. Tools: Hosting Provider, SSL Labs
Validate XML Sitemap Coverage
Evidence required: compare the sitemap with indexable product, menu, location, seasonal, and core service pages. Pass condition: important canonical URLs are represented appropriately and obsolete or blocked URLs are not relied upon.
Fail condition: key pages are absent, malformed, or contradicted by indexing directives. Severity: Medium unless discovery of important pages is materially affected. Owner: Developer or SEO owner. Corrective action: regenerate and resubmit the sitemap after correcting URL rules. Validation: inspect the submitted sitemap and representative URLs in Search Console. Tools: Google Search Console