SEO & GEO Audit · June 2026
Next.js launch at www.flowgear.net — Google AI, ChatGPT, Perplexity, and Claude
We audited 237 URLs from sitemap.xml on the new Next.js site (Build 2026.06.28). The homepage has a strong title, meta description, canonical, Open Graph (including og:image), single H1, and Organization JSON-LD in the root layout. Connector templates include FAQPage schema. Remaining work is mostly meta snippet quality on thin pages, page-specific social images (many routes still use /og/default.png), WebSite schema, legacy WordPress redirects, and optional llms.txt for Lens B.
For Google AI, crawl and snippet eligibility look healthy. For ChatGPT, Perplexity, and Claude, prioritize extractability on hub pages, entity consistency (sameAs), and customer-story corroboration — documented in the boost summary without mandating visible copy changes.
Verdict: materially better on technical baseline. Materially better technical foundation on the Next.js launch: default social images, Organization schema, FAQPage on connectors, and a curated 237-URL sitemap. Remaining work is meta snippet quality on thin pages, page-specific OG assets, WebSite schema, legacy redirects, and optional on-page GEO depth (review lane).
og:image tasks from the WordPress crawl.H1, headings, body, CTAs — suggestions only, not in Codex prompt. 202 items.
Review UIStructural GEO opportunities (authority, extractability patterns).
Boost summaryDomain: https://www.flowgear.net · URLs: 237 · Pages with tasks: 233
Handoff: meta, alt, schema, OG assets, redirects, llms.txt · Review lane: visible copy and GEO depth (optional)
Advisory only — no visible copy changes unless you approve items from the on-page review lane.
sameAs.Next.js site uses product-led titles; keep original POV on hub pages.
Review on-page copy suggestions for answer-first intros on hub pages.
Add descriptive alt text where flagged in handoff tasks.
Add dateModified on blog posts when content is updated.
Optional: add source links on blog and solution pages for Lens B.
Homepage and platform pages include product metrics; extend on blog where relevant.
Customer stories are strongest citation surface; link from hub pages.
Connector pages include FAQPage schema; extend to pricing/platform if visible FAQs exist.
robots.txt allows crawling; maintain canonical URLs on all indexable routes.
No broad LLM bot blocks detected; review if policy changes.
Optional /llms.txt for Perplexity and other Lens B tools.
Next.js App Router; verify forms and booking flows expose clear labels.
llms.txt — optional for ChatGPT/Perplexity; not a Google AI Overviews ranking factor.
FAQPage schema — rich results + Lens B extractability when visible FAQ content exists; not required for AI Overviews.
AI tone rewrites — do not rewrite on-page copy for algorithms; Flowgear copy is approved as-is.
Fan-out query pages — avoid thin programmatic URL spam; the 237-URL sitemap is appropriately curated.
SEO (Lens A) covers crawlability, indexation, snippet quality, and structured data for Google Search and Google AI features backed by the index. GEO (Lens B) covers how ChatGPT, Perplexity, Claude, and Copilot retrieve, cite, and summarise your content — crawler access, extractability, entity clarity, citations, and optional files like llms.txt. This audit tags tasks by platform where advice diverges.