adegagaucha.com — SEO + GEO Audit

CWV (Core Web Vitals) — Google's UX metrics: LCP (load), INP (responsiveness), CLS (visual stability). They feed ranking + the Technical score.

LCP — Largest Contentful Paint — when the largest element renders. Good <2.5s, Poor ≥4.0s. Driven mostly by server response time (TTFB).

INP / CLS — INP = Interaction-to-Next-Paint (target <200ms, replaced FID). CLS = layout shift (target <0.1).

GEO / AEO — Generative / Answer Engine Optimization — being citable by AI engines (ChatGPT, Perplexity, Gemini, AI Overviews), not just ranking in blue links.

llms.txt — An emerging 2026 manifest that tells LLMs which URLs to read. A broken/missing one costs AI-citation coverage.

AI crawler access — Whether bots like GPTBot / ClaudeBot / PerplexityBot are allowed in robots.txt. Blocking them removes you from AI answers.

Schema (structured data) — JSON-LD that labels your content (Article, FAQ, Organization, Person…). Helps both rich results and AI extraction.

Canonical — The <link rel="canonical"> tag declaring the preferred URL for a page — prevents duplicate-content dilution.

Striking distance — Keywords ranking on page 2 (positions 11-20) with real impressions — small wins can push them to page 1.

Crawl budget — How many pages a search engine will fetch per visit. Wasted on junk URLs = important pages crawled less often.

E-E-A-T — Experience, Expertise, Authoritativeness, Trustworthiness — Google's content-quality framework.

Evidence: curl homepage = 300,787 bytes HTML; grep <p = 10, <h1/<h2 = 12; grep 'div id="root|app"' = 0 (no SPA shell); meta robots content="follow, index, max-snippet:-1, max-image-preview:large"; canonical href="https://adegagaucha.com/" (self-referencing)

Impact: Highest-weight GEO factor passes: GPTBot/ClaudeBot/PerplexityBot (no JS execution) receive full content in initial HTML. No remediation needed; maintain SSR — do not migrate to a client-rendered theme.

Evidence: curl -sI https://adegagaucha.com/ | grep -iE 'Content-Security|X-Frame' returned EMPTY (both ABSENT). Present headers: Strict-Transport-Security: max-age=31536000, X-Content-Type-Options: nosniff, X-XSS-Protection: 1; mode=block, Permissions-Policy: geolocation=(), microphone=(),

Impact: Missing CSP = elevated XSS exposure; missing X-Frame-Options = clickjacking exposure. Security headers are a trust signal but have minimal direct ranking/GEO weight, hence P2 not P1.

Evidence: curl -sI homepage: 'Referrer-Policy: no-referrer-when-downgrade' (sends full referrer to any HTTPS destination; only withholds on HTTPS->HTTP downgrade)

Impact: Minor privacy/data-leakage; no SEO/GEO ranking impact. Low priority.

Evidence: robots.txt: 'Disallow: /adega-gaucha-locations/'. curl -sI /adega-gaucha-locations/ = HTTP/1.1 301 -> Location: /locations/. Live page curl -sI /locations/ = HTTP/1.1 200, NOT in robots Disallow (grep 'Disallow: /locations' = empty). Sitemap contains /locations/orlando/, /locatio

Impact: NOT harmful to local-SEO indexation: the three live location pages are 200, unblocked, and in-sitemap. The block targets an old redirecting slug only. Cleanup avoids future confusion and prevents accidental crawl-budget signals on a redirect.

Evidence: grep on 300KB homepage HTML: stylesheet links = 33; <script tags total = 75; external src scripts = 33 of which only 2 lack defer/async (31/33 deferred — good); font preloads (rel=preload as=font) = 0; preconnect/dns-prefetch = 7. Stack: Elementor Pro + ElementsKit + GutenKit + W

Impact: Render-blocking CSS is the top LCP risk on this page (static signal only — live CWV measured by separate agent). Builder bloat inflates critical request chain. Confidence on user-facing CWV impact is MEDIUM without field data per accuracy rule 3.

Evidence: curl --compressed -D - => Content-Encoding: gzip (server falls back to gzip even when 'br' requested in Accept-Encoding). Response line: HTTP/1.1 200 OK with header 'Upgrade: h2,h2c' (server advertises HTTP/2 but did not negotiate it on request). Vary: Accept-Encoding present.

Impact: Brotli typically yields ~15-20% smaller text payloads vs gzip; HTTP/2 multiplexing helps the long request chain (33 CSS + 33 JS). Both improve transfer speed for this asset-heavy page. No correctness/indexation impact.

Evidence: meta robots = index,follow; canonical = self-referencing https://adegagaucha.com/; http://adegagaucha.com/ -> 301 https://adegagaucha.com/ (HTTPS enforced); HSTS max-age=31536000 present; hreflang alternate tags = 3 (en, pt, es via Weglot). X-Robots-Tag: noindex appears only on s

Impact: Core indexability signals are healthy for both Google and AI crawlers. Multilingual hreflang correctly declared.

Evidence: grep '<h1' tmp/home.html -> 2 matches at byte 112828 and 260310. H1#1=[The Modern<br>Brazilian Steakhouse]; H1#2=[🌷 This Mother’s Day, surprise her with Adega Gaucha’s legendary Churrasco Experience. The best gift isn’t wrapped, it’s grilled!] (class='elementor-heading-title')

Impact: Splits the page's primary topical/keyword signal between the brand-defining hero and a transient promo headline, diluting relevance for 'Brazilian steakhouse Florida'. A single H1 is a long-standing on-page best practice.

Evidence: Homepage H1#2 text='This Mother’s Day, surprise her with Adega Gaucha’s legendary Churrasco Experience'. Mother's Day 2026 was 2026-05-10; audit date 2026-06-03. og:updated_time='2026-05-28T09:48:33-04:00'.

Impact: Outdated seasonal content in the most prominent heading position signals poor freshness to users and crawlers and wastes prime above-the-fold real estate ~3 weeks after the event passed.

Evidence: page-sitemap.xml lists legacy URLs e.g. /wine-list/, /orlando/, /kissimmee/, /brunch-menu/, /lunch-menu/, /bar-menu/, /desserts-menu/, /buffet/, /churrascotogo/. curl -I /wine-list/ -> 'HTTP/1.1 301 Moved Permanently, Location: /menu/wine-list/'; /orlando/ -> 301 -> /locations/or

Impact: Sitemaps should contain only canonical 200-status URLs. Listing 301-redirecting URLs wastes crawl budget, sends Google mixed signals about preferred URLs, and can slow consolidation of the clean URL structure.

Evidence: tmp/menu.html <title>='Our Menu – Brazilian Steakhouse in Orlando, Kissimmee and Deerfield Beach' = 73 chars (>~60 char / ~580px desktop truncation threshold).

Impact: Title likely truncated in Google results, hiding 'Deerfield Beach' and weakening CTR for that location's queries.

Evidence: grep -i 'BreadcrumbList' tmp/home.html -> 0; grep -i 'breadcrumb' tmp/home.html -> 0. Schema types present: Restaurant x2, WebSite, WebPage, AggregateRating, OpeningHoursSpecification, PostalAddress x4, GeoCoordinates x2, Place, SearchAction — no BreadcrumbList.

Impact: Misses breadcrumb rich-result eligibility in SERPs and the navigational/hierarchy clarity that helps Google understand the deep /locations/* and /menu/* structure.

Evidence: tmp/home.html: <link rel='alternate' href='https://adegagaucha.com/' hreflang='en'/>, hreflang='pt' (/pt/), hreflang='es' (/es/). grep -i 'x-default' -> 0.

Impact: Without x-default, Google has no explicit fallback for locales not in the en/pt/es set; low impact given en is the de-facto default, but it is an incomplete hreflang cluster.

Evidence: Only match for 'todo' in tmp/home.html: 'width: 100%; /* Ocupa todo el ancho del contenedor */' ('takes up the full width of the container'). No standalone 'TODO' placeholder string exists. grep '\btodo\b' -> 1 (this comment).

Impact: No SEO impact — inline CSS comment, not visible content. Documented here to correct the upstream regex false-positive so it is not actioned as a content defect.

Evidence: tmp/home.html: og:image='.../Adega_Gaucha_Logo_Avatar-1024x1024.png', og:image:alt='steakhouse'. twitter:card='summary_large_image' paired with a square 800x800 logo.

Impact: Weak social/link-preview appeal; a square logo on a summary_large_image card and a one-word alt under-sell click-throughs from shared links.

Evidence: grep of /menu.html and /menu/orlando/ for Picanha, Filet Mignon, Feijoada, Caipirinha, Salad Bar, Pao de Queijo, Sausage, Beef, Pork = 0 each; 'Picanha:3' on Orlando page is only inside img alt='...Picanha Churrasco'; '$[0-9]' price patterns = 0; menu links resolve to https://www

Impact: Local long-tail dish/price queries ('picanha orlando', 'brazilian steakhouse menu prices kissimmee') and AI assistants (ChatGPT/Perplexity/AI Overviews) cannot read or cite the menu. Largest organic + AI-visibility gap on the site.

Evidence: grep '"@type":"(Menu|MenuItem|MenuSection)"' = 0 on /menu.html and /menu/orlando/. Menu pages carry only Restaurant/Place/Breadcrumb/WebPage schema.

Impact: Misses Restaurant menu rich results and structured menu data that AI engines use to answer 'what's on the menu / what does X cost' queries.

Evidence: /menu H1='Our Menus' (1), H2 count=3 (Each Location Its Own Culinary Experience / ENJOY WITH US / HOST YOUR EVENTS), H3 count=3 (Orlando/Kissimmee/Deerfield Beach). churrascaria=0, rodizio=0 on /menu. Body is location routers + events CTA, no dishes.

Impact: Page ranks weakly for 'brazilian steakhouse menu orlando' class queries because it offers no substantive menu answer; intent (see the menu) is unmet on-page.

Evidence: Homepage H2 'FAQs About Dining At Adega Gaucha' present in heading list; grep '"@type":"(FAQPage|Question|Answer)"' on /home.html = 0; no itemprop acceptedAnswer markup found.

Impact: Forgoes FAQ rich-result eligibility and easy AI-answer extraction for high-intent local dining questions already written on the page.

Evidence: grep '<h1' on /home.html returns 2: '<h1>' -> 'The Modern Brazilian Steakhouse' (valid) and '<h1 class="elementor-heading-title elementor-size-default">' which strips to empty text.

Impact: Diluted/ambiguous H1 signal; an empty H1 is a wasted primary heading and minor accessibility issue.

Evidence: /menu and /menu-adega-gaucha-brazilian-steakhouse-orlando/ return byte-identical 189449-byte pages; both canonical to https://adegagaucha.com/menu/ (so the brief's URL is non-canonical but correctly points to /menu/). hreflang present en/pt/es on both pages but grep 'x-default' =

Impact: Multiple live URLs for the same page risk minor dilution if both are linked/indexed; missing x-default weakens international/Weglot signal for unmatched locales.

Evidence: /home.html 23 <img>; alt='' count = 5 (includes leading hero images). Good alts exist on others ('Adega Gaucha Brazilian Steakhouse Picanha Churrasco', 'Open Table Diners Choice award 2023 2024 2025', 'Dinner').

Impact: Missed image-SEO + accessibility on above-fold hero; lost opportunity for location/keyword-bearing alt text.

Evidence: /menu.html img alts: 'Adega Gaucha' repeated x4, and a malformed 'Adega_Gaucha_Group Dinin Events Orlando Host Steakhouse' (typo 'Dinin', underscores).

Impact: Low descriptive value and a visible typo in alt text; minor image-SEO/accessibility loss.

Evidence: Node A @id 'https://adegagaucha.com/#organization' @type [Restaurant,Organization]: priceRange '50-100', telephone '+14072504455', addressCountry 'USA'. Node B @id 'https://adegagaucha.com/#schema-130589' @type Restaurant: priceRange '80-150', telephone '14072504455', addressCoun

Impact: Two competing Restaurant nodes confuse Google entity resolution and AI knowledge-graph builders; conflicting priceRange and telephone create NAP inconsistency that can suppress rich results and erode local trust signals.

Evidence: #organization node: "sameAs": [ "https://www.facebook.com/adega.gaucha" ]. No Instagram, Google Business Profile, TripAdvisor, Yelp, Wikidata, Wikipedia, LinkedIn, OpenTable, or YouTube. sameAs absent entirely from the #schema-130589 Restaurant node.

Impact: sameAs is the single highest-leverage GEO property for cross-platform entity resolution. With only Facebook, AI models (ChatGPT, Perplexity, Gemini, AI Overviews) cannot confidently link Adega Gaucha across platforms or verify it as a recognized entity, weakening citation likelih

Evidence: All geo/address nodes point to Orlando: Place node streetAddress '8204 Crystal Clear Ln', geo 28.448804,-81.400653. The #schema-130589 description text reads 'in Orlando, Kissimmee, and Deerfield Beach' but no PostalAddress/GeoCoordinates/Restaurant node exists for Kissimmee or D

Impact: Two of three physical locations are invisible to local pack, Maps, and AI 'near me' queries. For a 3-location chain this is a major local-completeness gap directly costing discoverability in Kissimmee and Deerfield Beach markets.

Evidence: grep 'AggregateRating|ratingValue|reviewCount|ratingCount' across rank-math-schema JSON = 0 matches in all 6 nodes. (SHARED CONTEXT listed AggregateRating among homepage @types; not present in actual markup — recorded as ABSENT per evidence rule.)

Impact: No star-rating rich result eligibility and no review-strength signal for AI models. Review stars are a high-CTR SERP feature for restaurants; their absence forfeits a strong local trust signal.

Evidence: #schema-130589 servesCuisine array includes valid cuisines ('Brazilian Steakhouse','Churrascaria','South American Cuisine') BUT also non-cuisine entries: 'Reservations Accepted','Online Ordering Available','Happy Hour','Family Friendly Dining','Full Bar','Group Dining'. hasMenu '

Impact: Misusing servesCuisine as a feature dump dilutes the cuisine signal and is invalid per Schema.org (servesCuisine = cuisine type only). After GS1 merge, the canonical node would lose hasMenu/servesCuisine unless migrated.

Evidence: HTML head: <meta name="twitter:label1" content="Written by"> and <meta name="twitter:data1" content="Fabiano Borsato">. No Person node, no 'author' or 'founder' property anywhere in the @graph; 'Borsato' appears only in the twitter meta, not in JSON-LD.

Impact: Author/founder identity is an E-E-A-T and entity signal AI models use to attribute expertise and ground the brand to a real person. The signal exists as Twitter Card metadata but is not machine-linked in structured data.

Evidence: grep 'speakable' across rank-math-schema JSON = 0 matches on homepage. Absent on WebPage and Restaurant nodes.

Impact: speakable explicitly flags voice/AI-readable sections (hours, location, cuisine, reservations) — high-value for 'hey Google, what time does Adega Gaucha open' style assistant queries. Underused property; low effort, direct GEO/voice signal.

Evidence: #organization uses legacy openingHours strings with full day NAMES and 12h-style ranges: 'Monday 10:30-09:00','Tuesday,Wednesday,Thursday,Friday,Saturday 11:30-10:00','Sunday 11:00-09:00' (note 'Monday 10:30-09:00' implies close BEFORE open / overnight ambiguity). #schema-130589

Impact: openingHours strings should use ISO day codes (Mo,Tu) and 24h HH:MM; '10:30-09:00' is parse-ambiguous. The two nodes disagree on daily hours, producing conflicting hours signals for Google and assistants.

Evidence: Firecrawl found new.adegagaucha.com (HTTP 200, own robots, duplicates /blog /menu /rewards /our-team /lunch-menu /bar-menu /faqs), onlinemenu.adegagaucha.com (QuickQR menu), crm.adegagaucha.com (login indexed), kissimmee.adegagaucha.com/fr.

Impact: Eliminates duplicate-content dilution + wasted crawl budget

Evidence: Firecrawl: https://adegagaucha.com/blog_old title 'Blog & OLD'.

Impact: Removes duplicate blog surface

Evidence: Firecrawl: /kissimmee vs /locations/kissimmee; /lunch-menu vs /menu/lunch; /bar-menu vs /menu/bar; /birthday vs /offers/birthday; /brunch-menu vs /menu/brunch. ~24 301-redirecting URLs still in page-sitemap.xml.

Impact: Consolidates ranking signals; cleaner crawl

Evidence: Firecrawl: /dinner-menu-food-place-near-me, /cocktails-menu-restaurants-near-me.

Impact: Quality signal cleanup

Evidence: Lighthouse total-byte-weight = 8,078,017 bytes on homepage. 81% of GSC traffic is mobile.

Impact: Better mobile LCP on 4G; protects 18k mobile clicks/90d

Evidence: geo-technical grep: 33 render-blocking stylesheets + 75 script tags (Elementor/ElementsKit/GutenKit/WPVR).

Impact: Reduces main-thread + bytes; bloats mobile

Evidence: curl -I shows HTTP/1.1; Content-Encoding: gzip (no br).

Impact: Marginal transfer savings + multiplexing

Evidence: curl homepage = 300,787 bytes HTML; grep <p = 10, <h1/<h2 = 12; grep 'div id="root|app"' = 0 (no SPA shell); meta robots content="follow, index, max-snippet:-1, max-image-preview:large"; canonical href="https://adegagaucha.com/" (self-referencing)

Impact: Highest-weight GEO factor passes: GPTBot/ClaudeBot/PerplexityBot (no JS execution) receive full content in initial HTML. No remediation needed; maintain SSR — do not migrate to a client-rendered theme.

Evidence: curl -sI https://adegagaucha.com/ | grep -iE 'Content-Security|X-Frame' returned EMPTY (both ABSENT). Present headers: Strict-Transport-Security: max-age=31536000, X-Content-Type-Options: nosniff, X-XSS-Protection: 1; mode=block, Permissions-Policy: geolocation=(), microphone=(),

Impact: Missing CSP = elevated XSS exposure; missing X-Frame-Options = clickjacking exposure. Security headers are a trust signal but have minimal direct ranking/GEO weight, hence P2 not P1.

Evidence: curl -sI homepage: 'Referrer-Policy: no-referrer-when-downgrade' (sends full referrer to any HTTPS destination; only withholds on HTTPS->HTTP downgrade)

Impact: Minor privacy/data-leakage; no SEO/GEO ranking impact. Low priority.

Evidence: robots.txt: 'Disallow: /adega-gaucha-locations/'. curl -sI /adega-gaucha-locations/ = HTTP/1.1 301 -> Location: /locations/. Live page curl -sI /locations/ = HTTP/1.1 200, NOT in robots Disallow (grep 'Disallow: /locations' = empty). Sitemap contains /locations/orlando/, /locatio

Impact: NOT harmful to local-SEO indexation: the three live location pages are 200, unblocked, and in-sitemap. The block targets an old redirecting slug only. Cleanup avoids future confusion and prevents accidental crawl-budget signals on a redirect.

Evidence: grep on 300KB homepage HTML: stylesheet links = 33; <script tags total = 75; external src scripts = 33 of which only 2 lack defer/async (31/33 deferred — good); font preloads (rel=preload as=font) = 0; preconnect/dns-prefetch = 7. Stack: Elementor Pro + ElementsKit + GutenKit + W

Impact: Render-blocking CSS is the top LCP risk on this page (static signal only — live CWV measured by separate agent). Builder bloat inflates critical request chain. Confidence on user-facing CWV impact is MEDIUM without field data per accuracy rule 3.

Evidence: curl --compressed -D - => Content-Encoding: gzip (server falls back to gzip even when 'br' requested in Accept-Encoding). Response line: HTTP/1.1 200 OK with header 'Upgrade: h2,h2c' (server advertises HTTP/2 but did not negotiate it on request). Vary: Accept-Encoding present.

Impact: Brotli typically yields ~15-20% smaller text payloads vs gzip; HTTP/2 multiplexing helps the long request chain (33 CSS + 33 JS). Both improve transfer speed for this asset-heavy page. No correctness/indexation impact.

Evidence: meta robots = index,follow; canonical = self-referencing https://adegagaucha.com/; http://adegagaucha.com/ -> 301 https://adegagaucha.com/ (HTTPS enforced); HSTS max-age=31536000 present; hreflang alternate tags = 3 (en, pt, es via Weglot). X-Robots-Tag: noindex appears only on s

Impact: Core indexability signals are healthy for both Google and AI crawlers. Multilingual hreflang correctly declared.

Evidence: GSC 90d: 'brazilian steakhouse' 21,385 imp @ pos 7.8 / 1.8% CTR; 'brazilian steakhouse orlando' 16,720 imp @ pos 6.9; 'brazilian steakhouse near me' 8,223 imp @ pos 7.8. 167 queries in pos 5-20.

Impact: Moving the 3 non-branded heads from pos ~7 to pos 3 ~= +3-5k incremental clicks/90d

Evidence: GSC: /menu/ 1,366 clk / 111,037 imp / pos 6.7 (1.2% CTR); menu dish/price text not in HTML (getsauce.com widget).

Impact: Crawlable menu could lift CTR and capture dish-level + near-me queries

Evidence: GSC top pages: /deerfieldbeach?utm_source=google_profile&utm_campaign=localo&utm_medium=mainlink = 2,952 clicks (indexed ranking URL with tracking params).

Impact: Param URL competes with clean canonical; dilutes signals

Evidence: GSC: /menu/, /adega-gaucha-menus/ (66,280 imp pos 3.3), /menu-adega-gaucha-brazilian-steakhouse-orlando/, /menu/dinner/, /menu/lunch/ all rank for menu intent.

Impact: Consolidating equity to one menu hub improves rank stability

Evidence: curl -sL https://adegagaucha.com/llms.txt -> '<!DOCTYPE html><html lang=en-US>...<title>Adega Gaucha...' (Rank Math homepage markup), not text/markdown.

Impact: A real llms.txt guides AI crawlers to menu, locations, reservations, about

Evidence: Menu items/prices absent from HTML (getsauce.com widget).

Impact: Unlocks menu/price AI answers

Evidence: curl https://adegagaucha.com/llms.txt returns full WordPress homepage HTML, not llms.txt markdown.

Impact: Clean AI site map of key pages

Evidence: @graph Organization sameAs=['https://www.facebook.com/adega.gaucha'] only. No Instagram, TripAdvisor, Yelp, OpenTable, Google Business, Wikidata, LinkedIn.

Impact: Stronger entity disambiguation -> better AI citations + knowledge panel

Evidence: Firecrawl page copy: 'Proud Winners of OpenTable Diners Choice 2024, TripAdvisor Travelers Choice 2023/2024/2025, and Best of Florida 2023'; hosted Yelp Elite event.

Impact: Surfacing awards in schema/About strengthens E-E-A-T + AI trust

Evidence: On-site sameAs lists only Facebook; off-site awards exist but unconsolidated. Direct backlink metrics UNAVAILABLE.

Impact: Local link building likely needed to lift non-branded heads (seo-google SG1)

Evidence: Lighthouse total-byte-weight = 8,078,017 bytes on homepage. 81% of GSC traffic is mobile.

Impact: Better mobile LCP on 4G; protects 18k mobile clicks/90d

Evidence: geo-technical grep: 33 render-blocking stylesheets + 75 script tags (Elementor/ElementsKit/GutenKit/WPVR).

Impact: Reduces main-thread + bytes; bloats mobile

Evidence: curl -I shows HTTP/1.1; Content-Encoding: gzip (no br).

Impact: Marginal transfer savings + multiplexing

Evidence: grep -oicE '<main[ >]' = 0; '<header[ >]' = 0 (home). Present: <nav> x4, <footer> x1. Menu page also 0 main / 0 header.

Impact: Screen-reader users cannot jump to primary content via landmark navigation (WCAG 1.3.1 / ARIA landmark best practice); machine document-outline / GEO content extraction is weaker without a <main> content boundary.

Evidence: grep '<h1[ >]' = 2. Byte offset of <html>: 16 and 210452. Nested doc at line 3101: '<!DOCTYPE html><html lang="en"><head>...<title>Adega Gaucha | FAQs</title>'. Second H1 belongs to this nested document.

Impact: Two H1s confuse screen-reader heading navigation and dilute the topical H1 signal for SEO; a nested <html>/<head>/<title> inside <body> is invalid HTML and the embedded lang="en" conflicts with the page lang="en-US", harming assistive-tech language detection and crawler parsing.

Evidence: grep '<label' = 0 vs '<input' = 3. Inputs: subscribe-form full_name (placeholder 'First & Last Name', required), email (placeholder 'Email Address', required), search field (placeholder 'enter search term'). No for/id or aria-label on the inputs themselves.

Impact: Placeholder text is not a programmatic label; it disappears on input and is unreliable for screen readers (WCAG 1.3.1 Info & Relationships, 3.3.2 Labels or Instructions, 4.1.2 Name/Role/Value). Affects the birthday/email subscribe form and site search.

Evidence: grep for 'skip-to-content|skip-link|#content...skip' = 0 matches on homepage.

Impact: Keyboard and screen-reader users must tab through the full nav (4 <nav> blocks) on every page load to reach content (WCAG 2.4.1 Bypass Blocks).

Evidence: Heading sequence on home: h1 h2 h3 h3 h3 h4 h5 h2 h5 h2 h5 h5 h5 h5 h2 h2 h3 h2 h3 h5 h2 h5 h2 h2 h2 h1 h3. Multiple h2->h5 jumps; h6 count = 0.

Impact: Non-sequential headings break the logical document outline for screen-reader heading navigation (WCAG 1.3.1) and weaken content-structure signals used by AI extractors/GEO.

Evidence: grep '<nav class="adega-menu">' has no aria-label; footer navs (ag-footer-nav, ag-footer-legal) also unlabeled. Positive: 12 aria-label values on social/CTA (Facebook, Instagram, 'Birthday gift — claim yours', etc.) and 7 accordion buttons expose aria-expanded.

Impact: Multiple <nav> elements without distinct aria-labels are announced identically ('navigation') to screen readers, reducing wayfinding (WCAG 1.3.1 / ARIA practice). Low severity since labels exist elsewhere.

Evidence: Home: 43 <img> total, 34 with non-empty alt, 9 with alt="" (valid decorative), 0 with no alt attribute. 20.9% lack a descriptive alt but all are explicitly marked decorative. Menu page: 6/6 images have non-empty alt (100%).

Impact: Minor. Empty alt on truly decorative images is WCAG-correct. Risk only if any of the 9 decorative-marked images actually convey content (e.g., logo, dish photos) — that would be a 1.1.1 failure.

Evidence: Homepage 300KB, 16 lazy images + 4 fetchpriority=high (per shared context); hero H1 'The Modern Brazilian Steakhouse' is real text (good), but cannot confirm whether hero/section background images embed marketing copy without rendering.

Impact: If promotional text (hours, offers, location names) is baked into hero/section images, it is invisible to screen readers and to AI/GEO text extraction (WCAG 1.4.5 Images of Text).

Evidence: grep for cookiebot|onetrust|complianz|cookie-law-info|borlabs|iubenda|termly|cookie-notice|wp-gdpr|cookieyes|moove_gdpr on homepage returned ZERO matches, while GTM-5WVCNNKW (gtm.js) and activecampaign site_tracking.js both load on page load.

Impact: CCPA (FL business serving CA visitors) and GDPR (Weglot multilingual implies EU/intl visitors) both expect notice + opt-out/consent before non-essential tracking. Trackers fire pre-consent. Legal/trust exposure; California 'Do Not Sell/Share' opt-out not offered.

Evidence: robots.txt: 'Disallow: /privacy-policy/'. But page HTML meta: robots content="follow, index, max-snippet:-1...". Page returns HTTP 200 and is user-accessible.

Impact: A privacy policy SHOULD be openly indexable/accessible for compliance and trust signals; blocking it in robots.txt while the page itself says 'index' is a contradictory signal and weakens transparency. Crawlers cannot read it to corroborate trust/E-E-A-T.

Evidence: robots.txt: 'Disallow: /terms-of-use/'. Page HTML meta: robots content="follow, noindex". Page returns HTTP 200.

Impact: Terms are accessible to users (200) but deliberately kept out of the index. Lower compliance impact than privacy policy, but still a transparency/trust signal best left accessible to crawlers.

Evidence: WebFetch of /privacy-policy/: terms PRESENT = 'cookies, pixel tags, and other online tracking technologies', SMS opt-out (reply STOP), contact it@adegagaucha.com. Terms ABSENT = GDPR, CCPA, California Consumer Privacy Act, 'Do Not Sell', Google Analytics, data rights.

Impact: Policy admits tracking-tech use but provides no CCPA disclosures (right to know/delete/opt-out of sale-share) and no GDPR lawful-basis/data-subject-rights section. For a FL business with multilingual (intl) reach, both regimes are plausibly in scope.

Evidence: Homepage grep: type="email" input + ActiveCampaign plugin present; robots.txt also blocks /birthdayform/. ActiveCampaign site_tracking.js loads. No CMP/consent checkbox detected in homepage grep.

Impact: Email + birthday (potentially DOB) collection via ActiveCampaign with site-wide tracking but no detected consent checkbox or privacy-policy link at point of collection raises CCPA/GDPR consent-and-notice concerns, especially for the birthday form (could imply age/minor data).

Evidence: Response headers: 'Strict-Transport-Security: max-age=31536000' and 'X-Content-Type-Options: nosniff' present. No Content-Security-Policy and no X-Frame-Options header observed.

Impact: Transport security is solid (HSTS 1yr). Missing CSP/X-Frame-Options is a defense-in-depth hardening gap, not a privacy-law violation; low priority given third-party tag footprint is small (GTM + AC).

Evidence: grep '<h1' tmp/home.html -> 2 matches at byte 112828 and 260310. H1#1=[The Modern<br>Brazilian Steakhouse]; H1#2=[🌷 This Mother’s Day, surprise her with Adega Gaucha’s legendary Churrasco Experience. The best gift isn’t wrapped, it’s grilled!] (class='elementor-heading-title')

Impact: Splits the page's primary topical/keyword signal between the brand-defining hero and a transient promo headline, diluting relevance for 'Brazilian steakhouse Florida'. A single H1 is a long-standing on-page best practice.

Evidence: Homepage H1#2 text='This Mother’s Day, surprise her with Adega Gaucha’s legendary Churrasco Experience'. Mother's Day 2026 was 2026-05-10; audit date 2026-06-03. og:updated_time='2026-05-28T09:48:33-04:00'.

Impact: Outdated seasonal content in the most prominent heading position signals poor freshness to users and crawlers and wastes prime above-the-fold real estate ~3 weeks after the event passed.

Evidence: page-sitemap.xml lists legacy URLs e.g. /wine-list/, /orlando/, /kissimmee/, /brunch-menu/, /lunch-menu/, /bar-menu/, /desserts-menu/, /buffet/, /churrascotogo/. curl -I /wine-list/ -> 'HTTP/1.1 301 Moved Permanently, Location: /menu/wine-list/'; /orlando/ -> 301 -> /locations/or

Impact: Sitemaps should contain only canonical 200-status URLs. Listing 301-redirecting URLs wastes crawl budget, sends Google mixed signals about preferred URLs, and can slow consolidation of the clean URL structure.

Evidence: tmp/menu.html <title>='Our Menu – Brazilian Steakhouse in Orlando, Kissimmee and Deerfield Beach' = 73 chars (>~60 char / ~580px desktop truncation threshold).

Impact: Title likely truncated in Google results, hiding 'Deerfield Beach' and weakening CTR for that location's queries.

Evidence: grep -i 'BreadcrumbList' tmp/home.html -> 0; grep -i 'breadcrumb' tmp/home.html -> 0. Schema types present: Restaurant x2, WebSite, WebPage, AggregateRating, OpeningHoursSpecification, PostalAddress x4, GeoCoordinates x2, Place, SearchAction — no BreadcrumbList.

Impact: Misses breadcrumb rich-result eligibility in SERPs and the navigational/hierarchy clarity that helps Google understand the deep /locations/* and /menu/* structure.

Evidence: tmp/home.html: <link rel='alternate' href='https://adegagaucha.com/' hreflang='en'/>, hreflang='pt' (/pt/), hreflang='es' (/es/). grep -i 'x-default' -> 0.

Impact: Without x-default, Google has no explicit fallback for locales not in the en/pt/es set; low impact given en is the de-facto default, but it is an incomplete hreflang cluster.

Evidence: Only match for 'todo' in tmp/home.html: 'width: 100%; /* Ocupa todo el ancho del contenedor */' ('takes up the full width of the container'). No standalone 'TODO' placeholder string exists. grep '\btodo\b' -> 1 (this comment).

Impact: No SEO impact — inline CSS comment, not visible content. Documented here to correct the upstream regex false-positive so it is not actioned as a content defect.

Evidence: tmp/home.html: og:image='.../Adega_Gaucha_Logo_Avatar-1024x1024.png', og:image:alt='steakhouse'. twitter:card='summary_large_image' paired with a square 800x800 logo.

Impact: Weak social/link-preview appeal; a square logo on a summary_large_image card and a one-word alt under-sell click-throughs from shared links.

Evidence: GSC 90d: 'brazilian steakhouse' 21,385 imp @ pos 7.8 / 1.8% CTR; 'brazilian steakhouse orlando' 16,720 imp @ pos 6.9; 'brazilian steakhouse near me' 8,223 imp @ pos 7.8. 167 queries in pos 5-20.

Impact: Moving the 3 non-branded heads from pos ~7 to pos 3 ~= +3-5k incremental clicks/90d

Evidence: GSC: /menu/ 1,366 clk / 111,037 imp / pos 6.7 (1.2% CTR); menu dish/price text not in HTML (getsauce.com widget).

Impact: Crawlable menu could lift CTR and capture dish-level + near-me queries

Evidence: GSC top pages: /deerfieldbeach?utm_source=google_profile&utm_campaign=localo&utm_medium=mainlink = 2,952 clicks (indexed ranking URL with tracking params).

Impact: Param URL competes with clean canonical; dilutes signals

Evidence: GSC: /menu/, /adega-gaucha-menus/ (66,280 imp pos 3.3), /menu-adega-gaucha-brazilian-steakhouse-orlando/, /menu/dinner/, /menu/lunch/ all rank for menu intent.

Impact: Consolidating equity to one menu hub improves rank stability

Evidence: grep of /menu.html and /menu/orlando/ for Picanha, Filet Mignon, Feijoada, Caipirinha, Salad Bar, Pao de Queijo, Sausage, Beef, Pork = 0 each; 'Picanha:3' on Orlando page is only inside img alt='...Picanha Churrasco'; '$[0-9]' price patterns = 0; menu links resolve to https://www

Impact: Local long-tail dish/price queries ('picanha orlando', 'brazilian steakhouse menu prices kissimmee') and AI assistants (ChatGPT/Perplexity/AI Overviews) cannot read or cite the menu. Largest organic + AI-visibility gap on the site.

Evidence: grep '"@type":"(Menu|MenuItem|MenuSection)"' = 0 on /menu.html and /menu/orlando/. Menu pages carry only Restaurant/Place/Breadcrumb/WebPage schema.

Impact: Misses Restaurant menu rich results and structured menu data that AI engines use to answer 'what's on the menu / what does X cost' queries.

Evidence: /menu H1='Our Menus' (1), H2 count=3 (Each Location Its Own Culinary Experience / ENJOY WITH US / HOST YOUR EVENTS), H3 count=3 (Orlando/Kissimmee/Deerfield Beach). churrascaria=0, rodizio=0 on /menu. Body is location routers + events CTA, no dishes.

Impact: Page ranks weakly for 'brazilian steakhouse menu orlando' class queries because it offers no substantive menu answer; intent (see the menu) is unmet on-page.

Evidence: Homepage H2 'FAQs About Dining At Adega Gaucha' present in heading list; grep '"@type":"(FAQPage|Question|Answer)"' on /home.html = 0; no itemprop acceptedAnswer markup found.

Impact: Forgoes FAQ rich-result eligibility and easy AI-answer extraction for high-intent local dining questions already written on the page.

Evidence: grep '<h1' on /home.html returns 2: '<h1>' -> 'The Modern Brazilian Steakhouse' (valid) and '<h1 class="elementor-heading-title elementor-size-default">' which strips to empty text.

Impact: Diluted/ambiguous H1 signal; an empty H1 is a wasted primary heading and minor accessibility issue.

Evidence: /menu and /menu-adega-gaucha-brazilian-steakhouse-orlando/ return byte-identical 189449-byte pages; both canonical to https://adegagaucha.com/menu/ (so the brief's URL is non-canonical but correctly points to /menu/). hreflang present en/pt/es on both pages but grep 'x-default' =

Impact: Multiple live URLs for the same page risk minor dilution if both are linked/indexed; missing x-default weakens international/Weglot signal for unmatched locales.

Evidence: /home.html 23 <img>; alt='' count = 5 (includes leading hero images). Good alts exist on others ('Adega Gaucha Brazilian Steakhouse Picanha Churrasco', 'Open Table Diners Choice award 2023 2024 2025', 'Dinner').

Impact: Missed image-SEO + accessibility on above-fold hero; lost opportunity for location/keyword-bearing alt text.

Evidence: /menu.html img alts: 'Adega Gaucha' repeated x4, and a malformed 'Adega_Gaucha_Group Dinin Events Orlando Host Steakhouse' (typo 'Dinin', underscores).

Impact: Low descriptive value and a visible typo in alt text; minor image-SEO/accessibility loss.

Evidence: DOM query via Playwright returns 2 H1 elements: (1) 'THE MODERN BRAZILIAN STEAKHOUSE' at rect.top=213px (hero section); (2) 'This Mother's Day, surprise her with Adega Gaucha's legendary Churrasco Experience...' at rect.top=0 — rendered as the topmost element, likely a sticky pro

Impact: Google's Googlebot reads the promo H1 first in DOM order and may weight it as the page topic signal, diluting the brand/keyword H1. Seasonal H1 creates repeated crawl-time topic drift. Known 2-H1 issue confirmed.

Evidence: One <img> tag carries both fetchpriority='high' and a lazy-load plugin data-lazy-srcset pattern. At Playwright networkidle, src resolves to an SVG placeholder (data:image/svg+xml...) with natural_w=150, natural_h=150 — actual image not fetched. The fetchpriority=high signal is wa

Impact: Browser priority scheduler elevates an SVG placeholder to high fetch priority, potentially delaying true LCP candidate. Real award badge images (trust signals) load late, harming perceived load quality and potential LCP score.

Evidence: HTML source contains two <link rel='preload' as='image' href='Capture.jpg'> tags for the same URL: one with fetchpriority='high' (WP Rocket), one without. The hero element is a <video class='ag-hero__video'> with poster='Capture.jpg' — making Capture.jpg the probable LCP candidat

Impact: Duplicate preload wastes one browser preload slot and may cause a double-fetch depending on browser cache keying. No video preload means first-frame display depends on video stream buffering. Cross-origin subdomain adds DNS/TLS round-trip for video. JPEG poster is larger than equ

Evidence: Source contains 9 Google Fonts <link> tags total; 4 are rel='stylesheet' (render-blocking). Two distinct font bundles are each requested twice: Bundle A (Inter/Oswald/Jost/Playfair Display) appears as both a WP Rocket preload and a direct stylesheet; Bundle B (Montserrat/Varela R

Impact: Each render-blocking stylesheet adds a network round-trip on the critical path. Duplicate requests mean the browser may issue redundant fetches before cache kicks in. Loading 10+ font families across 2 bundles increases FOUT/FOIT window — visible text flash during hero load. This

Evidence: Playwright mobile (375x812) DOM query: CTA text 'book your table now' has rect={x:0, y:0, width:0, height:0, top:0}. The element exists and visible_atf=true only because coordinates are 0,0 — but zero width/height means no rendered tap surface. Separately, 'Menu' and 'Order now'

Impact: If the primary mobile reservation CTA (book your table now) has no rendered dimensions, mobile users cannot tap it. This directly breaks the primary conversion path on mobile. Google's mobile-first index evaluates mobile usability; a zero-size CTA may also trigger Core Web Vitals

Evidence: Desktop screenshot (1280x720) shows 'THE MODERN BRAZILIAN STEAKHOUSE' in white text over a darkened food-photography video frame. Contrast ratio not measured (no automated contrast tool invoked). H1 is the dominant above-the-fold text element at ~213px from top. Mobile screenshot

Impact: If video frame brightens at certain timestamps, H1 text may fall below WCAG AA 4.5:1 ratio. Low contrast on primary H1 is an accessibility issue and can indirectly affect engagement metrics.

Evidence: HTML source grep finds 5 WPVR/360-tour string references (likely in CSS/JS asset URLs). Playwright DOM query returns 0 iframes on homepage (only GTM noscript iframe). No WPVR shortcode found in rendered HTML. Plugin is loaded but 360-tour not embedded on homepage.

Impact: WPVR JS/CSS assets may still be enqueued globally (adding payload), but no live CLS risk from an unrendered iframe. If tour pages do embed WPVR iframes without explicit width/height attributes, those pages will have CLS risk. Homepage CLS risk from WPVR is not confirmed.

Evidence: Source grep returns 33 <link rel='stylesheet'> tags in homepage HTML. This includes Elementor base/pro, Weglot, multiple plugin stylesheets. While WP Rocket minifies/combines some, the Google Fonts 4 render-blocking requests remain separate. Large stylesheet count increases criti

Impact: Each additional stylesheet is a potential render-blocking resource. At 33 total, even with deferred loading for non-critical sheets, the sheer volume increases the probability of render-blocking and delays FCP. This is background pressure on all Core Web Vitals, not an isolated i