Executive Summary
High-level overview of tribal-lounge.com's SEO health and top priorities — goal: maximise local discovery across Gran Canaria
Key Findings
Tribal Lounge is a beachfront cocktail bar & restaurant in Playa del Inglés (San Bartolomé de Tirajana, Gran Canaria) built on WordPress + Divi. The 5 core pages (Home, Food, Drinks, Gallery, Contact) are indexable, canonicalised correctly and backed by detailed menus — the Food and Drinks pages alone carry an enormous amount of relevant text. But the site is still wearing pieces of the demo theme it was built from. A leftover /mailchimp page is live and indexable showing placeholder content — "1234 Divi St. #1000 San Francisco, CA", a US phone number "(234) 213-7574" and "Lorem ipsum" — and the default WordPress /sample-page ("bike messenger by day… XYZ Doohickey Company") is also indexable and sitting in the sitemap. On every page the contact block displays info@tribal-lounge.com but the actual mailto: link points to info@divicocktailbar.com, so every email click goes to the wrong address. The phone number changes between +34 928 50 14 72 (header) and 928 312 885 (body/footer), the brand alternates between "Tribal Lounge" and "Tribal Beach", the homepage hero video throws "Format(s) not supported or source(s) not found", and there is no Restaurant / LocalBusiness structured data anywhere — only the default Yoast WebPage/WebSite graph. For a venue whose entire SEO opportunity is "tourists nearby searching Google & Maps", these NAP, trust and local-schema gaps are the headline story.
Top 3 Priorities
The highest-impact actions to take right now
1
Remove the leftover demo pages and clean the sitemap
Delete (or 301-redirect to the homepage) /mailchimp and /sample-page. Both are index,follow and listed in page-sitemap.xml, so Google can index a "San Francisco / Lorem ipsum / divicocktailbar.com" page and the default WordPress sample under your brand — terrible for trust and for local relevance signals.
Expected impact: removes brand-damaging indexable junk + conflicting NAP signals; cleans crawl/index footprint immediately.
Critical
2
Fix the email link and unify NAP (Name, Address, Phone) site-wide
Repoint every mailto: from info@divicocktailbar.com to info@tribal-lounge.com. Choose ONE phone number and ONE brand name ("Tribal Lounge" vs "Tribal Beach") and use them identically on every page, matching your Google Business Profile exactly.
Expected impact: recovers lost email enquiries; consistent NAP is a direct local-ranking factor.
Critical
3
Add Restaurant / LocalBusiness structured data + claim Google Business Profile
Add Restaurant JSON-LD with name, full address, geo coordinates, telephone, openingHours (open 365 days, breakfast 10:00, kitchen to 02:00), priceRange, servesCuisine, hasMenu and sameAs (social profiles). Pair it with a fully-completed, review-gathering Google Business Profile.
Expected impact: eligibility for rich results & stronger Map/local-pack presence — the #1 driver of footfall for a beach restaurant.
High
Page-by-Page Breakdown
Individual audit results for each crawled page (all 8 URLs in the sitemap)
| Page | Title (<title>) | Words* | H1 | Meta Desc | Schema | OG | Issues |
|---|
| / | Home - Tribal-Lounge Gran Canaria Beach Bar Club and Restaurant | ~547 | Generic | Short | Basic only | Full | 6 |
| /food-…-menu-beach | Food - Tribal-Lounge Gran Canaria Beach Bar Club and Restaurant | ~5,000 | Pass | Pass | Basic only | Full | 5 |
| /drinks-cocktails-… | Drinks - Tribal-Lounge Gran Canaria Beach Bar Club and Restaurant | ~6,120 | "Join Us" | Pass | Basic only | Full | 5 |
| /gallet-beach-bar-… | Gallery - Tribal-Lounge Gran Canaria Beach Bar Club and Restaurant | ~325 | Pass | Short | Basic only | Partial | 5 |
| /contact | Contact - Tribal-Lounge Gran Canaria Beach Bar Club and Restaurant | ~794 | Pass | Pass | Basic only | Partial | 6 |
| /privacy-policy | Privacy Policy - Tribal-Lounge… | ~1,350 | Pass | Pass | noindex ✓ | Full | 0 |
| /sample-page | Sample Page - Tribal-Lounge… | ~509 | Pass | Auto | Basic only | Full | Delete |
| /mailchimp | MAILCHIMP - Tribal-Lounge… | ~560 | Generic | Auto | Basic only | Full | Delete |
* Word counts are approximate (parsed from rendered HTML). Food & Drinks are inflated by full menu listings. "Basic only" schema = default Yoast WebPage/WebSite graph with no Restaurant/LocalBusiness type.
Hero video is broken
The homepage hero shows "Media error: Format(s) not supported or source(s) not found" for /wp-content/uploads/2022/04/Tribal-Lounge-Gran-Canaria.mp4. The first thing a visitor sees fails to load.
Re-encode/re-upload the MP4 (H.264/MP4, web-optimised) or replace with a poster image + hosted (YouTube/Vimeo) embed.
Email link points to the wrong address
Displayed text is info@tribal-lounge.com but the link is mailto:info@divicocktailbar.com (leftover from the Divi demo).
Fix the mailto: to info@tribal-lounge.com in the global footer/header template.
Generic H1 with no brand or location
The single H1 is "Cocktail Bar & Restaurant" — no "Tribal Lounge", no "Playa del Inglés / Gran Canaria".
e.g. "Tribal Lounge — Beachfront Cocktail Bar & Restaurant, Playa del Inglés".
6 of 8 images missing alt text
Most homepage images have empty alt attributes; none use loading="lazy"; hero/section art is PNG, not WebP.
Add descriptive, location-aware alt text; enable lazy-loading; serve WebP.
Meta description is short & generic
109 characters: "…serving sun loving customers from all around the world." No location keyword, no hook.
Rewrite to ~150 chars with "Playa del Inglés / Gran Canaria", cuisine and a CTA.
No Restaurant/LocalBusiness schema
Only the default Yoast WebPage/WebSite graph is present (verified in the raw HTML).
Add full Restaurant JSON-LD on the homepage (see Technical tab).
Excellent menu depth
Full starters→desserts menu (pizzas, steaks, seafood, ramen, burgers, paella, kids, sides). Lots of genuine, relevant text — a real asset.
Keep — this is your strongest content. Mark it up with Menu/MenuItem schema.
Wrong email link (site-wide template)
Same mailto:info@divicocktailbar.com bug in the footer.
Fixed once in the global template.
~8 of 16 images missing alt; no lazy-load
Dish photos lack alt text — a missed opportunity for image search ("wood fired pizza Gran Canaria" etc.).
Add dish-descriptive alt text; lazy-load gallery thumbnails.
Title not localised + typo in meta
Title is "Food - Tribal-Lounge…" (section word only); meta description says "every pallet" (should be "palate").
e.g. "Food Menu — Wood-Fired Pizza, Steaks & Seafood | Tribal Lounge, Playa del Inglés". Fix typo.
No menu / breadcrumb display, basic schema only
Breadcrumb exists in schema but isn't shown; no Menu structured data.
Surface breadcrumbs visually; add hasMenu → Menu → MenuSection/MenuItem.
H1 is "Join Us" — meaningless
The page's H1 is a generic call-to-action; the descriptive line "Cocktail Bar with beach views" is only an H2.
Promote a descriptive H1, e.g. "Cocktail Bar & Drinks Menu — Tribal Lounge, Playa del Inglés".
~13 of 14 images missing alt text
Cocktail photos (Drink1–4.png) have empty alt and are PNG, not WebP.
Add alt text per cocktail; convert to WebP; lazy-load.
Wrong email link (template)
Same divicocktailbar.com mailto.
Global fix.
Page last modified 2022; basic schema only
dateModified is 2022-05-16 — looks stale vs other pages refreshed in 2026.
Refresh content/date; add Menu schema for the drinks list.
Huge, relevant drinks content
Cocktails, beers, wines, spirits, soft/hot drinks — strong topical coverage.
Keep; structure with proper headings + anchor links.
URL slug typo: "gallet" instead of "gallery"
The Gallery page lives at /gallet-beach-bar-gran-canaria.
If changing the slug, 301-redirect the old URL to avoid losing any equity/links.
Thin supporting text (~325 words)
Mostly images with one intro line; little crawlable context.
Add captions and a short paragraph using location + "beach bar / terrace / sunset" terms.
Partial social tags
Missing og:description / twitter:description.
Complete OG/Twitter tags for clean social previews.
~40 images, no lazy-loading, JPG/PNG
A gallery is the heaviest page type; without lazy-load it hurts mobile load.
Lazy-load below-the-fold images; serve WebP; add alt text.
Meta description typo ("atmoshphere")
Quality signal; also short at ~105 chars.
Rewrite and proofread.
Two different phone numbers on one page
The body says "To book call: +34928501472" while a footer block says "Call: 928312885". A third number "(234) 213-7574" appears on /mailchimp.
Standardise on one number everywhere (and on Google Business Profile).
Wrong email link
Again mailto:info@divicocktailbar.com.
Global fix.
No embedded map
The contact page has a form but no Google Map — for a physical venue that's a UX + local-relevance miss.
Embed a Google Map pin of the Playa del Inglés location.
Broken hero video repeats here
Same MP4 error as the homepage.
Fix or remove the video module.
No LocalBusiness schema on the contact page
The most natural home for NAP + hours has only the default WebSite graph.
Add Restaurant/LocalBusiness with address, geo, openingHours.
Verify the contact form delivers
Confirm submissions reach a monitored inbox (given the wrong email link elsewhere).
Send a live test; add an autoresponder.
Correctly set to noindex
robots: noindex, follow and self-canonical — exactly right for a privacy page.
No action. (It's still standard WordPress boilerplate — optionally localise contact details.)
Default WordPress sample page is live & indexable
Content: "I'm a bike messenger by day, aspiring actor by night… I like piña coladas… The XYZ Doohickey Company… go to your dashboard to delete this page." It's index,follow and in the sitemap.
Delete the page in WordPress; let it 404/410 or 301 it to the homepage; remove from sitemap.
Leftover Divi demo page exposing fake details
Live & indexable, showing "1234 Divi St. #1000 San Francisco, CA 94220", "(234) 213-7574", "info@divicocktailbar.com" and "Lorem ipsum…". This is where the wrong email/phone originates.
Delete; remove from sitemap; 301 to homepage if it has any inbound links.
Site-Wide Issues
Cross-cutting problems that affect multiple pages at once
NAP & Brand Consistency (Local SEO)
Email link wrong on every page
Displayed info@tribal-lounge.com → actual link mailto:info@divicocktailbar.com sitewide.
One template fix corrects all pages.
Multiple phone numbers
+34 928 50 14 72 (header), 928 312 885 (body/footer), (234) 213-7574 (/mailchimp).
Pick one canonical number; mirror it on Google Business Profile, Facebook & Instagram.
Brand name flips between "Tribal Lounge" and "Tribal Beach"
Domain & titles say "Tribal Lounge"; the About text and logo files ("Tribal-Beach1.png") say "Tribal Beach".
Decide on one public-facing name; use it consistently across site, schema and social.
Facebook link looks unrelated
Social link points to facebook.com/welcometogcunsensored rather than an obvious "Tribal Lounge" page.
Verify it's the official page; update if not, and add it to sameAs in schema.
Index Hygiene & Duplicate/Thin Content
Two demo pages indexable & in the sitemap
/sample-page and /mailchimp are both index,follow and listed in page-sitemap.xml.
Delete both; remove from sitemap.
No duplicate titles or meta descriptions across real pages
Home/Food/Drinks/Gallery/Contact each have unique titles and descriptions — no cannibalisation detected.
Maintain uniqueness as you add pages.
Content typos reduce quality signals
"pallet" (palate), "atmoshphere", "occassion", "avilability", "prepaired", "coriande"; "Margarita" vs "Margherita".
Proofread all customer-facing copy.
Robots.txt & Sitemap
robots.txt is valid and open
User-agent: *, no disallows, and it references sitemap_index.xml — nothing important is blocked.
No action.
Sitemap includes junk URLs
page-sitemap.xml lists 8 URLs including /sample-page and /mailchimp.
Once deleted, regenerate the sitemap so only the 5 real pages (+ noindex'd privacy excluded) remain.
Internationalisation (your "multilingual / whole Gran Canaria" goal)
No real multilingual pages or hreflang
The language switcher is the client-side Google Translate widget. There are zero hreflang alternate tags and og:locale is only en_US — Google can't index DE/NL/SV/ES versions because they don't exist as crawlable URLs.
If you want non-English visibility, create real translated pages (WPML/Polylang) with proper hreflang, or accept English-only and target English + Spanish brand/landmark terms. Prioritise Spanish ("restaurante / chiringuito Playa del Inglés") + German given the tourist mix.
Security & Server Headers
Not verifiable in this audit
HTTPS is confirmed (all pages load over https://), but response headers (HSTS, CSP, X-Content-Type-Options, compression, caching) couldn't be inspected through the crawl proxy.
Check headers directly (e.g. securityheaders.com) and enable HSTS, gzip/brotli and sensible cache-control via the host/Cloudflare.
Technical SEO
Implementation, structured data and performance signals (WordPress 7.0 + Divi 4.27.6 + Yoast)
Implementation Checklist
✓
Self-referencing canonical tags on all real pages (verified in raw HTML)
✓
Valid robots.txt, open crawling, references sitemap
✓
XML sitemap present (sitemap_index.xml → page-sitemap.xml)
✓
Viewport meta present (mobile-responsive Divi theme)
!
Viewport disables zoom (maximum-scale=1.0, user-scalable=0) — accessibility (WCAG) issue
✗
No Restaurant/LocalBusiness/Organization schema (only default Yoast WebPage/WebSite graph)
✗
No image lazy-loading anywhere
✗
Images served as PNG/JPG, not WebP/AVIF
✗
Two demo pages indexable (/sample-page, /mailchimp)
✗
Broken homepage hero video (MP4 fails to play)
!
No real hreflang / multilingual URLs (Google Translate widget only)
!
Security headers & compression not verified — check at host level
Schema Markup Strategy
Add this Restaurant JSON-LD to the homepage (and a matching LocalBusiness on /contact)
{
"@context": "https://schema.org",
"@type": "Restaurant",
"name": "Tribal Lounge",
"image": "https://tribal-lounge.com/wp-content/uploads/2026/04/Tribal-Beach1.png",
"servesCuisine": ["Italian","Pizza","Steak","Seafood","Cocktails","International"],
"priceRange": "€€",
"telephone": "+34928501472",
"email": "info@tribal-lounge.com",
"url": "https://tribal-lounge.com/",
"address": {
"@type": "PostalAddress",
"streetAddress": "CC Anexo 2, Número 8, Local 5",
"addressLocality": "Playa del Inglés",
"addressRegion": "Las Palmas",
"postalCode": "35100",
"addressCountry": "ES"
},
"geo": { "@type": "GeoCoordinates", "latitude": 27.7606, "longitude": -15.5740 },
"openingHoursSpecification": [{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday","Saturday","Sunday"],
"opens": "10:00", "closes": "02:00"
}],
"acceptsReservations": true,
"hasMenu": "https://tribal-lounge.com/food-gran-canaria-steaks-seafood-desserts-menu-beach",
"sameAs": [
"https://instagram.com/_triballounge",
"https://www.facebook.com/<official-page>"
]
}
Verify the exact postcode and geo-coordinates against the venue's Google Business Profile before publishing. Add aggregateRating only if you can source it from genuine on-site reviews.
Performance Indicators
HTML-level signals (not a substitute for a live Core Web Vitals / PageSpeed test)
Heavy, unoptimised images
PNG hero/section art and 40+ gallery JPGs, no lazy-loading, no next-gen formats. The Gallery and menu pages will be the slowest on mobile.
Convert to WebP, compress, add loading="lazy" and explicit width/height. A caching/optimisation plugin or Cloudflare Polish helps.
Divi adds large inline CSS/JS
Each page ships ~180–240 KB of inlined head CSS. Typical of Divi but worth taming.
Enable Divi's "Dynamic CSS / Critical CSS" + defer non-critical JS; run PageSpeed Insights for real LCP/CLS.
Run a live speed test
Core Web Vitals can't be measured from HTML alone.
Benchmark Home, Food and Gallery in PageSpeed Insights; target LCP < 2.5s on mobile.
Content & Keyword Strategy
You chose "analyse & suggest" — here are the targets, clusters and gaps for local Gran Canaria discovery
Inferred Keyword Map
What each page currently targets vs. what it should target
| Page | Current focus | Recommended primary target | Location in title? |
|---|
| / | "Cocktail Bar & Restaurant" | beach bar / restaurant Playa del Inglés (Gran Canaria) | No city |
| /food-… | Food menu | wood-fired pizza / steak / restaurant Playa del Inglés | No city |
| /drinks-… | Drinks menu | cocktail bar Playa del Inglés / Maspalomas | No city |
| /gallet-… | Gallery | beachfront bar Gran Canaria (photos) | Region only |
| /contact | Contact / booking | book a table / private parties Playa del Inglés | No city |
Recommended Keyword Targets
Grouped by intent. Validate exact volumes in your own Keywords Explorer — Ahrefs Site Explorer wasn't accessible on the connected plan.
Local + category (highest priority):
beach bar playa del inglésrestaurants playa del inglésbeachfront restaurant gran canariacocktail bar maspalomaswhere to eat playa del inglésbest restaurants maspalomasbeach club gran canariarestaurant on the beach gran canaria
Cuisine / dish-led:
wood fired pizza playa del inglésitalian restaurant maspalomassteak restaurant gran canariaseafood playa del ingléspaella gran canariagourmet burger maspalomasbeach brunch gran canariabreakfast playa del inglés
Experience / occasion & Spanish:
live dj bar playa del ingléssunset cocktails gran canariaprivate party venue gran canariagroup booking restaurant maspalomasrestaurante playa del ingléschiringuito playa del inglésdónde comer en playa del inglésstrandbar playa del inglés (DE)
Semantic / LSI Terms to Weave In
Green = already used on the site · Red = largely missing, add these
cocktailswood-fired ovenNeapolitan pizzasteaksseafoodbrunchlive DJPlaya del Inglésterraceprivate parties
Maspalomasbeachfront / sea viewsunsetSan Bartolomé de Tirajanachiringuitoreservations / book a tablevegetarian & vegan optionsgluten-freedog-friendlyopen 365 daysfamily-friendlyhappy hour
Recommended Content Clusters
Give Google a clear "beach restaurant in Playa del Inglés" topic structure
Pillar: Beach Bar & Restaurant — Playa del Inglés
/ (Home — local pillar)
/food (menu)
/drinks (cocktails)
/gallery
/contact (book a table)
Content Gap Recommendations
New pages/posts to capture "things to do / where to eat" tourist demand (your stated goal: more local visitors)
1
A proper "About / Our Story" page
Craig & Bobby, the move from England, the wood-fired oven, the beachfront terrace — real E-E-A-T and brand story. Resolve the Tribal Lounge vs Tribal Beach name here.
2
Local guide posts
e.g. "Best beachfront brunch in Playa del Inglés", "Where to watch the sunset with a cocktail in Maspalomas", "Late-night eats in Playa del Inglés (open till 2am)". These rank for tourist research queries and funnel to the menu.
3
Dedicated "Private parties & events" + "Reservations" pages
You seat 80 and do private parties — give that its own indexable page with a clear enquiry CTA, plus a reservations page targeting "book a table" intent.
Internal Linking Analysis
Link distribution across the audited pages (approximate — based on nav, footer and in-content links)
Link Equity Distribution
Every real page is reachable from the global nav (good for such a small site); the two demo pages are orphaned
| Page | Incoming (internal) | Outgoing (internal) | Status |
|---|
| / | High (logo + nav on every page) | ~7 | Healthy |
| /food-… | High (nav + home/gallery CTAs) | ~6 | Healthy |
| /drinks-… | High (nav + home/gallery CTAs) | ~6 | Healthy |
| /gallet-… | Nav only | ~8 | Healthy |
| /contact | Nav only | ~6 | Healthy |
| /privacy-policy | Footer only | ~6 | OK (noindex) |
| /sample-page | 0 | ~6 | Orphan |
| /mailchimp | 0 | ~6 | Orphan |
Orphan Pages
Pages with zero internal links — only reachable via the sitemap or a direct URL
/sample-page & /mailchimp
Neither is linked from the site, yet both are indexable and in the sitemap. They're "orphans" only because they're demo leftovers — the fix is deletion, not more links.
Delete both (see Action Plan).
Suggested Internal Links
Small wins to strengthen topical/contextual linking
1
Link Food ↔ Drinks contextually
The Food page mentions drinks and vice-versa — add in-body links ("see our full cocktail menu") beyond the nav.
2
Link Gallery → Contact ("book a table")
After browsing photos, the natural next step is booking. Add a clear CTA link.
3
Future blog → menu/contact links
When the local guides go live, link them down to Food, Drinks and Contact to pass relevance and funnel visitors.
Prioritised Action Plan
Ranked by impact and grouped by effort
Quick Wins — under 1 hour each
1
Delete /sample-page and /mailchimp
Remove in WordPress; regenerate the sitemap. Optionally 301 to the homepage.
Kills brand-damaging indexable junk + a source of wrong NAP.
2
Fix the site-wide email link
Change mailto:info@divicocktailbar.com → info@tribal-lounge.com in the global template (Divi footer/header).
Stops losing every email enquiry.
3
Pick one phone number & one brand name
Use +34 928 50 14 72 (or whichever is correct) and "Tribal Lounge" everywhere; match Google Business Profile.
Consistent NAP = better local ranking + trust.
4
Remove the zoom restriction
Drop maximum-scale=1.0, user-scalable=0 from the viewport meta.
Fixes a WCAG accessibility fail.
5
Proofread customer-facing copy
Fix "pallet→palate", "atmoshphere", "occassion", "avilability", "Margarita/Margherita".
Cleaner quality/E-E-A-T signals.
High Impact — 1–4 hours each
6
Add Restaurant/LocalBusiness JSON-LD
Use the snippet on the Technical tab (name, address, geo, phone, openingHours, priceRange, servesCuisine, hasMenu, sameAs).
Rich-result eligibility + stronger local/Map relevance.
7
Fix the homepage hero video
Re-encode the MP4 or swap for a poster image / hosted embed.
Repairs the first impression on Home + Contact.
8
Localise titles, meta descriptions & H1s
Put "Playa del Inglés / Maspalomas / Gran Canaria" + cuisine into titles; fix Drinks' "Join Us" H1 and the generic Home H1.
Directly targets the local searches you want to win.
9
Image SEO + performance pass
Add alt text everywhere, enable lazy-loading, convert to WebP, compress the gallery.
Faster mobile load + image-search visibility for dishes/cocktails.
10
Embed a Google Map on /contact & complete OG/Twitter tags
Add a map pin; fill missing og:description/twitter:description on Gallery & Contact.
Better UX, local relevance and social previews.
Strategic Initiatives — ongoing
11
Claim & optimise Google Business Profile + gather reviews
For a beach restaurant, GBP + reviews drive more footfall than the website itself. Match NAP exactly; post photos & offers weekly.
The single biggest local-discovery lever.
12
Decide the multilingual approach
Replace the Google Translate widget with real translated pages (WPML/Polylang) + hreflang for ES/DE (and NL/SV/NO if worthwhile), or commit to English + Spanish only.
Unlocks non-English tourist search across Gran Canaria.
13
Build local "where to eat / things to do" content
Add About + a handful of Playa del Inglés/Maspalomas guide posts that funnel to the menu and bookings.
Captures tourist research demand and builds topical authority.
14
Get listed & reviewed on the platforms tourists use
TripAdvisor, Google, The Fork/ElTenedor, Yelp — consistent NAP + links/citations.
Local citations + referral traffic + social proof.
Full Implementation Checklist
✗
Delete /sample-page & /mailchimp; regenerate sitemap
✗
Fix site-wide mailto → info@tribal-lounge.com
✗
Standardise one phone number across site + GBP + social
✗
Settle on one brand name (Tribal Lounge vs Tribal Beach)
✗
Add Restaurant/LocalBusiness JSON-LD (Home + Contact)
✗
Fix the homepage hero video
✗
Localise titles/meta/H1 (Playa del Inglés, Maspalomas, cuisine)
✗
Add image alt text; enable lazy-loading; convert to WebP
!
Remove viewport zoom restriction
!
Embed Google Map on /contact; complete OG/Twitter tags
!
Proofread all copy; fix typos
!
Verify contact form delivery + add autoresponder
!
Check security headers/compression at host (HSTS, gzip/brotli)
!
Decide multilingual strategy (real translations + hreflang)
!
Claim/optimise Google Business Profile; collect reviews
!
Add About page + local guide content; build citations
Audit method: rendered-HTML crawl of all 8 sitemap URLs (Firecrawl) + raw-HTML verification of canonical, hreflang and JSON-LD on Home/Food/Contact. Limitations: no live Core Web Vitals, backlink or ranking data (connected Ahrefs plan returned "insufficient plan" for Site Explorer). Generated June 4, 2026.