nextgrowth.ai — 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: CSS --global-palette1:#9b67e4 mapped to --global-palette-highlight (link color via 'a{color:var(--global-palette-highlight)}'). Computed ratio #9b67e4 on #ffffff = 3.85:1 (WCAG 1.4.3 requires >=4.5:1 for body-size text).

Impact: Inline body links are hard to read for low-vision users; AA body-text contrast violation = ADA/EAA exposure. Darken highlight palette to ~#7B4FD0 (>=4.5:1) or restrict #9b67e4 to large/bold text only.

Evidence: CSS --global-palette6:#718096. Computed ratio on #ffffff = 4.02:1 vs 4.5:1 required (WCAG 1.4.3). Used for muted/meta text in Kadence theme.

Impact: Secondary/meta text (dates, captions) misses AA by a small margin. Shift to ~#5E6B7E (>=4.5:1) for body-size usage.

Evidence: CSS --global-palette2:#00c9e8. On white = 2.0:1 (fails even large-text 3:1). On dark #0d172b = 8.96:1 (passes). Risk only if accent is ever applied as text on light backgrounds.

Impact: Conditional risk. Keep #00c9e8 for dark-bg/UI accents only; never as text on light surfaces. Confirm via live render where the token is applied.

Evidence: CSS has 72 :focus rule occurrences and only 1 :focus-visible; outline:0 appears 7x but all are gated (a:active{outline:0}, .hide-focus-outline *:focus, #primary[tabindex=-1]:focus) so no blanket removal found. Theme (Kadence) applies a:focus highlight color. Cannot confirm a perc

Impact: Likely compliant given gated outline rules, but keyboard focus visibility (WCAG 2.4.7) needs confirmation via real Tab-through. If any control lacks a visible ring, add :focus-visible{outline:2px solid #9b67e4;outline-offset:2px}.

Evidence: Static audit only; no Lighthouse a11y category and no Chrome DevTools keyboard run executed (DataForSEO/Chrome MCP not invoked). aria-expanded present on 2 menu toggles (good signal) but tab order, menu operability, and trap-free navigation unverified.

Impact: WCAG 2.1.1/2.1.2 unverified. Recommend a Lighthouse accessibility run (mcp on_page_lighthouse) or manual keyboard pass on nav + mobile menu toggle to confirm.

Evidence: Home newsletter input '<input class="formkit-input" name="email_address" type="email" aria-label="Email Address" required ...>' has no autocomplete attribute (0 inputs with autocomplete found across sampled pages).

Impact: Minor WCAG 2.2 AA gap. Add autocomplete="email" to the newsletter field to reduce redundant entry for users with cognitive/motor needs.

Evidence: Firecrawl: off-site = own FB + Gumroad + 1 VN group; no Reddit/YouTube/Wikipedia/HN/press

Impact: Independent mentions drive E-E-A-T + AI citation trust

Evidence: schema sameAs has FB/LinkedIn/GitHub/X/YouTube/Reddit, no Wikipedia/Wikidata

Impact: Entity disambiguation for AI

Evidence: GSC 'nextgrowth' pos 3.6

Impact: Entity baseline

Evidence: grep /tmp/ng_home.html: 'pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-5107575593357424' and 'googletagmanager.com/gtag/js?id=GT-P85WF39B' both present and loaded unconditionally; 0 matches for any consent library (cookieyes|onetrust|cookiebot|termly|iubend

Impact: Closes the single largest EU/CA exposure. AdSense personalized ads + GTM setting cookies pre-consent is the exact pattern behind CNIL/GDPR enforcement. Adding a Consent Mode v2 banner (Complianz/CookieYes free tier) gates both tags and lifts compliance score ~18pts.

Evidence: grep /privacy-policy: PASS for gdpr, ccpa, 'opt out', 'data retention', cookie, third-party, 'personal data', 'personal information'; FAIL for 'data subject', 'right to delete', 'right to access', 'data controller', 'legal basis'. URL: https://nextgrowth.ai/privacy-policy

Impact: Policy already names GDPR/CCPA and has contact@nextgrowth.ai + 'exercise your rights'; adding the explicit Art.15-22 rights list (access, deletion, rectification, portability), named data controller, and Art.6 legal basis brings it to audit-ready and reduces litigation surface.

Evidence: grep /privacy-policy: 0 matches for 'essential cookies|analytics cookies|marketing cookies|functional cookies|necessary cookies|performance cookies'; no consent banner present to surface categories. URL: https://nextgrowth.ai/

Impact: A consent banner (CM1 fix) with category toggles (necessary/analytics/marketing) plus a cookie table in the policy satisfies this; resolves alongside CM1.

Evidence: Headers expose WordPress (link: https://nextgrowth.ai/wp-json/) on LiteSpeed; plugin versions could not be enumerated (WP MCP not authenticated in this run). No stale dependency evidence either way. URL headers from https://nextgrowth.ai/

Impact: Run WP MCP get_active_plugins to enumerate versions and flag >90d-stale or CVE plugins; manual review needed, not a confirmed gap.

Evidence: curl /llms.txt 200, 5727 bytes, Author+Topics+Pillars+links

Impact: Helps AI parse site + author authority

Evidence: only llms.txt present

Impact: Deeper AI ingestion

Evidence: Schema FAQ+Speakable + crawler access vs GSC avg pos 27.5

Impact: Page-1 moves unlock AIO/Perplexity citations

Evidence: No Bing Webmaster connection

Impact: Confirm Copilot surface

Evidence: robots allows GPTBot/ClaudeBot/PerplexityBot/Google-Extended; llms.txt 200

Impact: Eligible across ChatGPT/Claude/Perplexity/Gemini

Evidence: https://nextgrowth.ai/ + all posts (grep JSON-LD): Person '#thenguyen' (sameAs LinkedIn the-nguyen-devops, jobTitle 'Senior DevOps Engineer and SEO Automation Specialist', knowsAbout array) coexists with a second Person '@id=https://nextgrowth.ai/author/nextgrowth/' (sameAs Linke

Impact: Same-entity nodes with conflicting @id/sameAs/jobTitle prevent reliable entity resolution; AI models may treat them as two different people/orgs or distrust the identity signal. Consolidate to a single canonical @id per entity.

Evidence: https://nextgrowth.ai/ai-overview-seo-guide/ raw HTML: "cssSelector":[".entry-content > p:first-of-type","h1",".tl-dr"] — the child combinator '>' is emitted as the literal entity '>' inside the JSON-LD string, so the selector cannot match. Present on every BlogPosting samp

Impact: speakable targeting silently fails on the first-paragraph selector; voice/AI-assistant readability markup does not resolve. Output a raw '>' (or use a descendant selector) in the JSON-LD string.

Evidence: https://nextgrowth.ai/ JSON-LD: Organization/Person sameAs = LinkedIn, GitHub, Twitter/X, Facebook (4 platforms on #thenguyen); Block 1 Organization drops Twitter and adds Reddit. grep wikipedia|wikidata over homepage HTML = 0 matches.

Impact: Wikipedia/Wikidata are the strongest cross-platform entity-linking signals for GEO; absence limits AI entity-graph confidence. Add Wikidata (create if needed) and unify the Twitter/X + Reddit links across all nodes.

Evidence: https://nextgrowth.ai/ai-overview-seo-guide/ BlogPosting #richSnippet has headline, image, datePublished, dateModified, author(@id), publisher(@id), mainEntityOfPage, description, articleSection — but wordCount is MISSING (verified across sampled posts).

Impact: wordCount is a minor recommended property that helps AI models gauge content depth; low-effort add to the existing BlogPosting template.

Evidence: https://nextgrowth.ai/ai-overview-seo-guide/#faq, /aeo-vs-geo-vs-seo-explained/#faq, /what-is-n8n/#faq all contain FAQPage. Google restricts FAQ rich results to government/health authorities since Aug 2023.

Impact: No harm and still useful for AI Q&A extraction; keep it. No action required beyond awareness that it will not render as a Google rich result.

Evidence: curl https://nextgrowth.ai/ -> 200, content-type text/html, server: LiteSpeed; raw HTML strip-tags = 45,889 chars visible text, 23 <p>, 1 <h1>, 20 <h2>; grep __NEXT_DATA__|__NUXT__ = 0; no <div id=root|app|__next>. Sample article https://nextgrowth.ai/seo-content-optimization-gui

Impact: Positive: GPTBot/ClaudeBot/PerplexityBot (which do not execute JS) can index all primary content. No remediation needed; protect this in any future re-platform.

Evidence: https://nextgrowth.ai/robots.txt (200): Allow / for GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-Web, PerplexityBot, Google-Extended, Applebot-Extended, Amazonbot, Cohere-ai, YouBot, Meta-ExternalAgent; Disallow / for CCBot, Bytespider, Diffbot, Omgili. Sitemap: https:/

Impact: Positive: maximizes AI-search visibility (GEO) while controlling abusive scrapers. Verify CCBot block is intentional (CCBot feeds some training/aggregation; some publishers allow it).

Evidence: Response headers from curl -D - https://nextgrowth.ai/ include HSTS, X-Frame-Options SAMEORIGIN, X-Content-Type-Options nosniff, Referrer-Policy strict-origin-when-cross-origin, Permissions-Policy — but NO content-security-policy header present.

Impact: Minor XSS hardening gap. All other security headers present, so trust-signal impact on SEO is negligible; add a CSP for defense-in-depth.

Evidence: curl https://www.nextgrowth.ai/ -> exit 60 SEC_E_WRONG_PRINCIPAL (cert SAN does not cover www). Apex http://nextgrowth.ai/ correctly 301 -> https://nextgrowth.ai/. Canonical is apex (self-referencing https://nextgrowth.ai/).

Impact: Users/links hitting https://www. get a TLS error instead of a redirect to the canonical apex. Add www to the certificate SAN (or a 301 host redirect with valid cert) to avoid broken entry points and link equity loss.

Evidence: grep /tmp/ng_home.html: <link rel=preload as=style onload="this.onload=null;this.rel='stylesheet'" href=.../litespeed/css/...>; rel=stylesheet count = 0 (all async); 4 <noscript> blocks present; 2 inline <style> blocks (critical CSS). 25 scripts: 16 defer, 2 async.

Impact: Static LCP-risk reducer (non-render-blocking CSS, critical CSS inlined). noscript fallback present so styled content is not JS-dependent. No action needed; CWV measurement is seo-performance's scope.

Evidence: curl https://nextgrowth.ai/llms.txt -> 200.

Impact: Positive GEO signal — provides an AI-oriented site map of key content. Validate contents in geo-llmstxt (out of scope here).

Evidence: grep /tmp/ng_home.html: <title> 'SEO Automation with n8n — NextGrowth.ai' (~38 chars, slightly under 50-60 ideal); meta description 152 chars; self-ref canonical; robots 'follow,index,max-image-preview:large'; viewport width=device-width,initial-scale=1; html lang=en-US; 13 og:*

Impact: Indexability and rich previews fully controlled. Optional: lengthen homepage <title> toward 50-60 chars to use more SERP real estate.

Evidence: https://nextgrowth.ai/sitemap_index.xml (200) valid XML, 2 child sitemaps w/ lastmod; post-sitemap.xml = 101 <url>, 101 <lastmod>, latest 2026-06-03 (today 2026-06-08). Target apex appears as canonical; article URLs present.

Impact: Healthy crawl guidance with trustworthy freshness dates. No action.

Evidence: https://nextgrowth.ai/on-page-seo-checklist <title>On-Page SEO Checklist 2026: 30 Items That Move Rankings | NG.ai</title> = 63 chars (grep-verified from rawHtml head). Home=39, About=49, dfs-vs-serpapi within range.

Impact: Minor pixel-width truncation risk on the brand suffix in Google SERPs; no ranking effect. Trim suffix or shorten to <=60 chars.

Evidence: grep over rawHtml: 2 of 23 (home), 2 of 8 (about), 2 of 44 (on-page post), images match alt="". No images are missing the alt attribute entirely (0 missing across all pages).

Impact: If decorative, empty alt is correct and is a non-issue; if content-bearing (e.g., hero/diagram) it loses image-search + a11y value. Spot-check the 2 per page and add descriptive alt where content-bearing.

Evidence: on-page post: 6 of 20 unique external links carry rel nofollow|sponsored; dfs-vs-serpapi: 6 of 11. Externals include vendor/comparison domains (dataforseo.com, serpapi.com, g2.com, capterra.com) alongside authority citations (developers.google.com, ahrefs.com).

Impact: Comparison/review posts link to commercial vendor pages; uncontrolled dofollow to vendors leaks equity and, if any are affiliate/sponsored, risks Google link-spam guideline non-compliance. Audit vendor links and apply rel="nofollow sponsored" where commercial; keep editorial cita

Evidence: grep home rawHtml: H1=1, H2=20, H3=0. Posts have correct nesting (on-page: H2=12/H3=42; about: H2=8/H3=8).

Impact: Flat H2 list on a long homepage is acceptable for a section-based landing layout; only revisit if any H2 sections grow sub-topics that warrant H3 nesting for outline clarity.

Evidence: grep across home/about/posts head: hreflang=(none). html lang=en-US, og:locale=en_US.

Impact: Correct for a single-locale English site; documented here as a deliberate non-issue. Only add hreflang if a localized version is launched.

Evidence: https://nextgrowth.ai/ — grep of <head>: name=.description count=0; og:description present = 'I automate SEO with n8n and share every workflow, result, and mistake publicly. 30+ articles published...'. Rank Math active (rank-math markers found) but did not emit a standard meta de

Impact: Google may auto-generate a less compelling SERP snippet for the homepage; a hand-written 150-160 char description improves CTR on the brand/primary query. Copy the existing og:description into Rank Math's meta description field.

Evidence: https://nextgrowth.ai/ — application/ld+json blocks=3; @type set after unescape = Organization, WebSite, SearchAction, WebPage, Person, CollectionPage, ImageObject. Schema is present and complete for a homepage; this is a NON-issue confirmation, no action needed.

Impact: No action required — homepage schema coverage (Organization + WebSite/SearchAction sitelinks-searchbox + Person) is already best-practice. Logged for completeness.

Evidence: https://nextgrowth.ai/ — H1 count=1 ('I'm Automating the Entire SEO Lifecycle with n8n.'), H2 count=20, H3 count=0.

Impact: Twenty sibling H2s with no nesting is acceptable for a landing/portfolio homepage but offers no semantic sub-grouping for assistive tech or AI extraction. Low priority; only refactor if sections grow.

Evidence: https://nextgrowth.ai/ — 23 <img> tags, 0 missing alt attribute, 2 with alt="". Empty alt is correct for decorative images; verify these 2 are truly decorative (icons/dividers) and not content images.

Impact: If the 2 empty-alt images are decorative this is correct accessibility practice. Only add descriptive alt if either conveys meaning.

Evidence: https://nextgrowth.ai/dataforseo-review/ — title 'DataForSEO Review 2026: Honest Verdict After 12 Weeks' (54 chars); meta description present (~157 chars); canonical self-referencing; robots 'follow, index, max-image-preview:large'; og:type=article; H1=1, H2=11, H3=37; 4 JSON-LD

Impact: No action needed. Use this post as the on-page template for other reviews/posts on the site.

Evidence: https://nextgrowth.ai/dataforseo-review/ — <title>='DataForSEO Review 2026: Honest Verdict After 12 Weeks'; H1='DataForSEO Reviews 2026: Is the Pay-As-You-Go API Worth It?'. Both contain the primary entity 'DataForSEO Review(s) 2026'.

Impact: Intentional title/H1 divergence is a valid tactic (title for SERP CTR, H1 for on-page). Singular vs plural 'Review/Reviews' is the only keyword nuance; harmless. No fix required.

Evidence: https://nextgrowth.ai/dataforseo-review/ — 37 <img> tags, 0 missing alt attribute, 2 alt="". All 37 have explicit width+height and WebP source.

Impact: Confirm the 2 empty-alt images are decorative; if any is a chart/screenshot conveying data, add descriptive alt for accessibility and image search.

Evidence: Home: lazyload=11, data-src=7 markers; loading="lazy" native=1. Post: lazyload=18, data-src=15; native=1. lazysizes/data-src pattern intentionally strips native lazy attr. Per skill guidance, do NOT flag as 'not lazy-loaded'.

Impact: Lazy loading is functioning via JS. No action. Logged so downstream agents do not double-report a false 'images not lazy-loaded' issue.

Evidence: https://nextgrowth.ai/on-page-seo-checklist <title>On-Page SEO Checklist 2026: 30 Items That Move Rankings | NG.ai</title> = 63 chars (grep-verified from rawHtml head). Home=39, About=49, dfs-vs-serpapi within range.

Impact: Minor pixel-width truncation risk on the brand suffix in Google SERPs; no ranking effect. Trim suffix or shorten to <=60 chars.

Evidence: grep over rawHtml: 2 of 23 (home), 2 of 8 (about), 2 of 44 (on-page post), images match alt="". No images are missing the alt attribute entirely (0 missing across all pages).

Impact: If decorative, empty alt is correct and is a non-issue; if content-bearing (e.g., hero/diagram) it loses image-search + a11y value. Spot-check the 2 per page and add descriptive alt where content-bearing.

Evidence: on-page post: 6 of 20 unique external links carry rel nofollow|sponsored; dfs-vs-serpapi: 6 of 11. Externals include vendor/comparison domains (dataforseo.com, serpapi.com, g2.com, capterra.com) alongside authority citations (developers.google.com, ahrefs.com).

Impact: Comparison/review posts link to commercial vendor pages; uncontrolled dofollow to vendors leaks equity and, if any are affiliate/sponsored, risks Google link-spam guideline non-compliance. Audit vendor links and apply rel="nofollow sponsored" where commercial; keep editorial cita

Evidence: grep home rawHtml: H1=1, H2=20, H3=0. Posts have correct nesting (on-page: H2=12/H3=42; about: H2=8/H3=8).

Impact: Flat H2 list on a long homepage is acceptable for a section-based landing layout; only revisit if any H2 sections grow sub-topics that warrant H3 nesting for outline clarity.

Evidence: grep across home/about/posts head: hreflang=(none). html lang=en-US, og:locale=en_US.

Impact: Correct for a single-locale English site; documented here as a deliberate non-issue. Only add hreflang if a localized version is launched.

Evidence: GSC 90d totals

Impact: Page-1 moves multiply clicks; traffic already converts at 22%

Evidence: GSC: /best-seo-api/ 78,557 imp @22.6 (and GA4 shows it converts 39%); 'seo api' 4,655 imp @26.6; 'dataforseo alternative' 1,030 imp @11.4

Impact: /best-seo-api/ rank lift = clicks x 39% conversion

Evidence: GA4: /what-is-n8n/ 34% conv, /best-seo-api/ 39%, /coolify-vs-dokploy/ 62% key-event rate

Impact: Prioritize internal links + refresh to these proven converters

Evidence: GSC sitemaps: page-sitemap.xml submitted 2025-08-27 vs post 2026-05-22

Impact: Faster recrawl

Evidence: GSC 'nextgrowth' pos 3.6

Impact: Brand entity established

Evidence: Lighthouse total-byte-weight=1,760,852; unused-css-rules=130

Impact: Lighter pages -> faster mobile LCP

Evidence: seo-visual: logo has loading=lazy, no fetchpriority/preload

Impact: Excluding LCP img from lazyload cuts LCP

Evidence: Lighthouse best-practices=0.77

Impact: Console/3rd-party cleanup

Evidence: Lighthouse LCP 1832ms, CLS 0.023, TBT 12ms

Impact: No desktop CWV remediation; confirm mobile

Evidence: https://nextgrowth.ai/ — grep of <head>: name=.description count=0; og:description present = 'I automate SEO with n8n and share every workflow, result, and mistake publicly. 30+ articles published...'. Rank Math active (rank-math markers found) but did not emit a standard meta de

Impact: Google may auto-generate a less compelling SERP snippet for the homepage; a hand-written 150-160 char description improves CTR on the brand/primary query. Copy the existing og:description into Rank Math's meta description field.

Evidence: https://nextgrowth.ai/ — application/ld+json blocks=3; @type set after unescape = Organization, WebSite, SearchAction, WebPage, Person, CollectionPage, ImageObject. Schema is present and complete for a homepage; this is a NON-issue confirmation, no action needed.

Impact: No action required — homepage schema coverage (Organization + WebSite/SearchAction sitelinks-searchbox + Person) is already best-practice. Logged for completeness.

Evidence: https://nextgrowth.ai/ — H1 count=1 ('I'm Automating the Entire SEO Lifecycle with n8n.'), H2 count=20, H3 count=0.

Impact: Twenty sibling H2s with no nesting is acceptable for a landing/portfolio homepage but offers no semantic sub-grouping for assistive tech or AI extraction. Low priority; only refactor if sections grow.

Evidence: https://nextgrowth.ai/ — 23 <img> tags, 0 missing alt attribute, 2 with alt="". Empty alt is correct for decorative images; verify these 2 are truly decorative (icons/dividers) and not content images.

Impact: If the 2 empty-alt images are decorative this is correct accessibility practice. Only add descriptive alt if either conveys meaning.

Evidence: https://nextgrowth.ai/dataforseo-review/ — title 'DataForSEO Review 2026: Honest Verdict After 12 Weeks' (54 chars); meta description present (~157 chars); canonical self-referencing; robots 'follow, index, max-image-preview:large'; og:type=article; H1=1, H2=11, H3=37; 4 JSON-LD

Impact: No action needed. Use this post as the on-page template for other reviews/posts on the site.

Evidence: https://nextgrowth.ai/dataforseo-review/ — <title>='DataForSEO Review 2026: Honest Verdict After 12 Weeks'; H1='DataForSEO Reviews 2026: Is the Pay-As-You-Go API Worth It?'. Both contain the primary entity 'DataForSEO Review(s) 2026'.

Impact: Intentional title/H1 divergence is a valid tactic (title for SERP CTR, H1 for on-page). Singular vs plural 'Review/Reviews' is the only keyword nuance; harmless. No fix required.

Evidence: https://nextgrowth.ai/dataforseo-review/ — 37 <img> tags, 0 missing alt attribute, 2 alt="". All 37 have explicit width+height and WebP source.

Impact: Confirm the 2 empty-alt images are decorative; if any is a chart/screenshot conveying data, add descriptive alt for accessibility and image search.

Evidence: Home: lazyload=11, data-src=7 markers; loading="lazy" native=1. Post: lazyload=18, data-src=15; native=1. lazysizes/data-src pattern intentionally strips native lazy attr. Per skill guidance, do NOT flag as 'not lazy-loaded'.

Impact: Lazy loading is functioning via JS. No action. Logged so downstream agents do not double-report a false 'images not lazy-loaded' issue.

Evidence: Lighthouse total-byte-weight=1,760,852; unused-css-rules=130

Impact: Lighter pages -> faster mobile LCP

Evidence: seo-visual: logo has loading=lazy, no fetchpriority/preload

Impact: Excluding LCP img from lazyload cuts LCP

Evidence: Lighthouse best-practices=0.77

Impact: Console/3rd-party cleanup

Evidence: Lighthouse LCP 1832ms, CLS 0.023, TBT 12ms

Impact: No desktop CWV remediation; confirm mobile

Evidence: curl https://nextgrowth.ai/ -> 200, content-type text/html, server: LiteSpeed; raw HTML strip-tags = 45,889 chars visible text, 23 <p>, 1 <h1>, 20 <h2>; grep __NEXT_DATA__|__NUXT__ = 0; no <div id=root|app|__next>. Sample article https://nextgrowth.ai/seo-content-optimization-gui

Impact: Positive: GPTBot/ClaudeBot/PerplexityBot (which do not execute JS) can index all primary content. No remediation needed; protect this in any future re-platform.

Evidence: https://nextgrowth.ai/robots.txt (200): Allow / for GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-Web, PerplexityBot, Google-Extended, Applebot-Extended, Amazonbot, Cohere-ai, YouBot, Meta-ExternalAgent; Disallow / for CCBot, Bytespider, Diffbot, Omgili. Sitemap: https:/

Impact: Positive: maximizes AI-search visibility (GEO) while controlling abusive scrapers. Verify CCBot block is intentional (CCBot feeds some training/aggregation; some publishers allow it).

Evidence: Response headers from curl -D - https://nextgrowth.ai/ include HSTS, X-Frame-Options SAMEORIGIN, X-Content-Type-Options nosniff, Referrer-Policy strict-origin-when-cross-origin, Permissions-Policy — but NO content-security-policy header present.

Impact: Minor XSS hardening gap. All other security headers present, so trust-signal impact on SEO is negligible; add a CSP for defense-in-depth.

Evidence: curl https://www.nextgrowth.ai/ -> exit 60 SEC_E_WRONG_PRINCIPAL (cert SAN does not cover www). Apex http://nextgrowth.ai/ correctly 301 -> https://nextgrowth.ai/. Canonical is apex (self-referencing https://nextgrowth.ai/).

Impact: Users/links hitting https://www. get a TLS error instead of a redirect to the canonical apex. Add www to the certificate SAN (or a 301 host redirect with valid cert) to avoid broken entry points and link equity loss.

Evidence: grep /tmp/ng_home.html: <link rel=preload as=style onload="this.onload=null;this.rel='stylesheet'" href=.../litespeed/css/...>; rel=stylesheet count = 0 (all async); 4 <noscript> blocks present; 2 inline <style> blocks (critical CSS). 25 scripts: 16 defer, 2 async.

Impact: Static LCP-risk reducer (non-render-blocking CSS, critical CSS inlined). noscript fallback present so styled content is not JS-dependent. No action needed; CWV measurement is seo-performance's scope.

Evidence: curl https://nextgrowth.ai/llms.txt -> 200.

Impact: Positive GEO signal — provides an AI-oriented site map of key content. Validate contents in geo-llmstxt (out of scope here).

Evidence: grep /tmp/ng_home.html: <title> 'SEO Automation with n8n — NextGrowth.ai' (~38 chars, slightly under 50-60 ideal); meta description 152 chars; self-ref canonical; robots 'follow,index,max-image-preview:large'; viewport width=device-width,initial-scale=1; html lang=en-US; 13 og:*

Impact: Indexability and rich previews fully controlled. Optional: lengthen homepage <title> toward 50-60 chars to use more SERP real estate.

Evidence: https://nextgrowth.ai/sitemap_index.xml (200) valid XML, 2 child sitemaps w/ lastmod; post-sitemap.xml = 101 <url>, 101 <lastmod>, latest 2026-06-03 (today 2026-06-08). Target apex appears as canonical; article URLs present.

Impact: Healthy crawl guidance with trustworthy freshness dates. No action.

Evidence: GSC 90d totals

Impact: Page-1 moves multiply clicks; traffic already converts at 22%

Evidence: GSC: /best-seo-api/ 78,557 imp @22.6 (and GA4 shows it converts 39%); 'seo api' 4,655 imp @26.6; 'dataforseo alternative' 1,030 imp @11.4

Impact: /best-seo-api/ rank lift = clicks x 39% conversion

Evidence: GA4: /what-is-n8n/ 34% conv, /best-seo-api/ 39%, /coolify-vs-dokploy/ 62% key-event rate

Impact: Prioritize internal links + refresh to these proven converters

Evidence: GSC sitemaps: page-sitemap.xml submitted 2025-08-27 vs post 2026-05-22

Impact: Faster recrawl

Evidence: GSC 'nextgrowth' pos 3.6

Impact: Brand entity established

Evidence: Crawl: indexable_not_in_sitemap=12

Impact: Complete discovery

Evidence: GSC last_submitted 2025-08-27

Impact: Faster recrawl

Evidence: Firecrawl map ~120 URLs; 5 /category/ hubs

Impact: Good clustering base

Evidence: DOM: img[alt='NextGrowth.ai logo'] has loading='lazy' and data-lazyloaded='1' attribute set by LiteSpeed Cache; no fetchpriority attribute; no <link rel=preload> for this image in <head>. Image renders at top:18px on desktop (inside 1080px viewport). This suppresses browser's pre

Impact: Delays LCP on every page load. Fix: remove loading='lazy' from the logo img (or set loading='eager') and add fetchpriority='high'. Add <link rel='preload' as='image'> in <head> for the .webp logo URL. In LiteSpeed Cache settings, exclude the logo image from lazy-load.

Evidence: DOM: header element computed style position='absolute', z-index=100, height=80px. Confirmed visually in desktop screenshot: nav floats over hero but is not sticky. On scroll the nav is lost entirely, making navigation require scrolling back to top.

Impact: Poor UX on long homepage (page is ~7226px tall on desktop). Returning to navigation requires full scroll-up. Fix: change header CSS to position:sticky; top:0 with appropriate z-index and background.

Evidence: Mobile DOM: 15+ category label links (e.g., 'SEO AUTOMATION', 'SEO TOOLS', 'N8N INFRASTRUCTURE', 'SEO FUNDAMENTALS', 'SETUP GUIDES') measured at w:230px h:19px. Google/WCAG recommends minimum 44x44px for interactive touch targets. These span the full card width but are only 19px

Impact: Increases mobile tap errors, hurts UX for a mobile audience. Fix: add padding-top/padding-bottom to category label anchor elements so rendered height reaches at least 44px, or increase line-height and padding in the card CSS.

Evidence: Mobile DOM: BUTTON text='Subscribe →' measured w:138px h:23px at top:11596. Tablet DOM: same button w:138px h:23px. On desktop the button is also small relative to the form field. This is distinct from the blog-card labels and likely a different component (email opt-in section).

Impact: Newsletter subscribe friction on mobile. Fix: add min-height:44px and vertical padding to the subscribe button style in the email opt-in widget.

Evidence: Head meta: og:image = 'https://nextgrowth.ai/wp-content/uploads/2026/03/Facebook-NextGrowth-1024x1024.png'; og:image:width=1024; og:image:height=1024. Facebook, LinkedIn, and Slack crop square OG images to landscape — the 1:1 square will be letter-boxed or cropped awkwardly. Twit

Impact: Reduced click-through when shared on social media. Fix: create a 1200x630px branded OG image and update og:image meta tag. Also add twitter:card='summary_large_image' if not present.

Evidence: DOM: <link rel='dns-prefetch' href='//fonts.googleapis.com'>. No preconnect link found for fonts.googleapis.com or fonts.gstatic.com (only dns-prefetch). Preconnect performs DNS+TCP+TLS handshake early; dns-prefetch only resolves DNS. Google's own recommendation for self-hosted o

Impact: Minor latency increase for font file fetch. Fix: replace dns-prefetch with two preconnect tags: one for fonts.googleapis.com and one for fonts.gstatic.com with crossorigin attribute. This is a theme-level or LiteSpeed Cache setting.

Evidence: DOM: Images at index 7-20 (all below fold, top > 4000px) have fetchpriority='high' with no lazy loading. Only 1 of 24 images has loading='lazy' (the logo). The LCP image (logo or hero text) has no preload hint. WordPress theme/plugin is incorrectly marking off-screen thumbnails a

Impact: Misaligned fetch priorities force browser to compete for bandwidth loading below-fold thumbnails during initial page load. This delays LCP. Fix: (1) add fetchpriority='high' to the logo / true LCP image only; (2) add loading='lazy' to all blog card thumbnail images; (3) audit the

Evidence: Mobile viewport 375x812: 'Get SEVOsmith' CTA bottom = 757px (55px above fold edge, passes). 'See The Roadmap' CTA top = 770px, which means it starts at 770px and likely extends to ~815px — partially off screen. H1 height on mobile is 212px (top:214), with body copy below that, pu

Impact: On small phones (SE, older Android) both CTAs may be fully below fold. Consider tightening hero section top padding or reducing body copy length above the CTA on mobile via CSS.