65
SEO audit for weddingnamechange.com
Wedding Name Change Kit — Pre-filled Forms, Letters & Checklist
Health 65/100 (fair) · 17 pages crawled · generated 2026-07-29
Download Markdown report (feed to ChatGPT / Claude / Cursor)Answer 12 questions, get your complete name-change kit: pre-filled government forms, ready-to-send letters for your banks and employer, and a step-by-step checklist in the right order. $29, instant, n…
17
pages crawled
15
indexable pages
0
errors
19
warnings
94
notices
0
orphan pages
0
broken links
Category breakdown
| Category | Score | Errors | Warnings | Notices |
|---|---|---|---|---|
| Titles | 75 | 0 | 14 | 0 |
| Budget | 96 | 0 | 2 | 0 |
| Content | 98 | 0 | 1 | 18 |
| Duplicate | 98 | 0 | 1 | 0 |
| Indexability | 98 | 0 | 1 | 0 |
| Agent Readiness | 100 | 0 | 0 | 2 |
| Cache | 100 | 0 | 0 | 2 |
| Crawlability | 100 | 0 | 0 | 1 |
| Images | 100 | 0 | 0 | 1 |
| Links | 100 | 0 | 0 | 4 |
| Meta Description | 100 | 0 | 0 | 15 |
| Performance | 100 | 0 | 0 | 20 |
| Security | 100 | 0 | 0 | 16 |
| Structured Data | 100 | 0 | 0 | 15 |
Findings
Warnings (6 rules)
warning robots.txt-disallowed URL receives internal links (crawl-budget leak)
Rule budget.disallow_linked · Budget · 1 occurrence(s)
- https://weddingnamechange.com/legal — internal links point to https://weddingnamechange.com/legal, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://weddingnamechange.com/, https://weddingnamechange.com/name-change-checklist, https://weddingnamechange.com/passport-photo.
warning Noindex page receives internal links (crawl-budget waste)
Rule budget.noindex_linked · Budget · 1 occurrence(s)
- https://weddingnamechange.com/recover — this noindex page has 16 internal inlink(s) — Googlebot follows them, fetches the page, then drops it unindexed, spending crawl budget for no indexing benefit (and the links leak equity). Remove/redirect the links, or drop the noindex if the page should be indexed. Linked from: https://weddingnamechange.com/, https://weddingnamechange.com/name-change-checklist, https://weddingnamechange.com/passport-photo.
warning Thin content (low word count)
Rule content.thin · Content · 1 occurrence(s)
warning Homepage duplicated across protocol/host variants (no redirect)
Rule duplicate.protocol_host · Duplicate · 1 occurrence(s)
- https://weddingnamechange.com/ — https://www.weddingnamechange.com/ serves the same homepage content with a 200 and no redirect — Google sees a duplicate. Pick one canonical host/scheme and 301-redirect the others.
warning Page is noindex
Rule index.noindex · Indexability · 1 occurrence(s)
- https://weddingnamechange.com/recover — meta/X-Robots: meta=noindex
warning Title likely truncated in SERP (too wide)
Rule title.too_long · Titles · 14 occurrence(s)
- https://weddingnamechange.com/married-name-generator — 86 chars, ~715px (limit ~580px)
- https://weddingnamechange.com/name-change-after-marriage — 80 chars, ~667px (limit ~580px)
- https://weddingnamechange.com/name-change-after-marriage/california — 85 chars, ~693px (limit ~580px)
- https://weddingnamechange.com/name-change-after-marriage/florida — 82 chars, ~675px (limit ~580px)
- https://weddingnamechange.com/name-change-after-marriage/georgia — 82 chars, ~681px (limit ~580px)
- https://weddingnamechange.com/name-change-after-marriage/illinois — 83 chars, ~671px (limit ~580px)
- https://weddingnamechange.com/name-change-after-marriage/michigan — 83 chars, ~691px (limit ~580px)
- https://weddingnamechange.com/name-change-after-marriage/new-york — 83 chars, ~696px (limit ~580px)
- https://weddingnamechange.com/name-change-after-marriage/north-carolina — 89 chars, ~729px (limit ~580px)
- https://weddingnamechange.com/name-change-after-marriage/ohio — 79 chars, ~657px (limit ~580px)
- https://weddingnamechange.com/name-change-after-marriage/pennsylvania — 87 chars, ~723px (limit ~580px)
- https://weddingnamechange.com/name-change-after-marriage/texas — 80 chars, ~670px (limit ~580px)
- https://weddingnamechange.com/name-change-checklist — 71 chars, ~587px (limit ~580px)
- https://weddingnamechange.com/passport-photo — 80 chars, ~660px (limit ~580px)
Notices (16 rules)
notice Heading levels skip a level
Rule agent.heading_skip · Agent Readiness · 1 occurrence(s)
- https://weddingnamechange.com/ — h3 follows h1 — skips h2
notice No llms.txt for AI agents
Rule agent.llms_txt_missing · Agent Readiness · 1 occurrence(s)
- https://weddingnamechange.com/ — no llms.txt found at the site root — add one so AI agents get a curated site summary
notice Page served uncached (no-store/private or CDN bypass)
Rule cache.not_cacheable · Cache · 2 occurrence(s)
- https://weddingnamechange.com/ — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate · vercel: MISS
- https://weddingnamechange.com/recover — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate · vercel: MISS
notice Low text-to-HTML ratio
Rule content.low_ratio · Content · 1 occurrence(s)
notice Main text is hard to read (low Flesch Reading Ease)
Rule content.readability_poor · Content · 1 occurrence(s)
- https://weddingnamechange.com/name-change-checklist — this page reads as difficult (Flesch Reading Ease 37, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
notice Likely hero image lacks fetchpriority=high
Rule images.hero_no_fetchpriority · Performance · 1 occurrence(s)
- https://weddingnamechange.com/ — the likely hero/LCP image (checklist.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
notice Images without width/height (layout shift / CLS)
Rule images.missing_dimensions · Images · 1 occurrence(s)
- https://weddingnamechange.com/ — 3 of 3 images without width/height
notice Page has only one internal inlink (fragile crawl path)
Rule links.single_inlink · Links · 4 occurrence(s)
- https://weddingnamechange.com/name-change-after-marriage/georgia — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.
- https://weddingnamechange.com/name-change-after-marriage/illinois — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.
- https://weddingnamechange.com/name-change-after-marriage/michigan — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.
- https://weddingnamechange.com/name-change-after-marriage/north-carolina — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.
notice Legacy <meta name=keywords> tag present (Google ignores it)
Rule meta.keywords_present · Content · 16 occurrence(s)
- https://weddingnamechange.com/ — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://weddingnamechange.com/married-name-generator — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://weddingnamechange.com/name-change-after-marriage — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://weddingnamechange.com/name-change-after-marriage/california — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://weddingnamechange.com/name-change-after-marriage/florida — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://weddingnamechange.com/name-change-after-marriage/georgia — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://weddingnamechange.com/name-change-after-marriage/illinois — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://weddingnamechange.com/name-change-after-marriage/michigan — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://weddingnamechange.com/name-change-after-marriage/new-york — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://weddingnamechange.com/name-change-after-marriage/north-carolina — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://weddingnamechange.com/name-change-after-marriage/ohio — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://weddingnamechange.com/name-change-after-marriage/pennsylvania — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://weddingnamechange.com/name-change-after-marriage/texas — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://weddingnamechange.com/name-change-checklist — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://weddingnamechange.com/passport-photo — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://weddingnamechange.com/recover — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
notice Meta description too long
Rule meta_desc.too_long · Meta Description · 15 occurrence(s)
- https://weddingnamechange.com/ — 215 chars
- https://weddingnamechange.com/married-name-generator — 179 chars
- https://weddingnamechange.com/name-change-after-marriage — 179 chars
- https://weddingnamechange.com/name-change-after-marriage/california — 185 chars
- https://weddingnamechange.com/name-change-after-marriage/florida — 182 chars
- https://weddingnamechange.com/name-change-after-marriage/georgia — 187 chars
- https://weddingnamechange.com/name-change-after-marriage/illinois — 183 chars
- https://weddingnamechange.com/name-change-after-marriage/michigan — 189 chars
- https://weddingnamechange.com/name-change-after-marriage/new-york — 183 chars
- https://weddingnamechange.com/name-change-after-marriage/north-carolina — 188 chars
- https://weddingnamechange.com/name-change-after-marriage/ohio — 181 chars
- https://weddingnamechange.com/name-change-after-marriage/pennsylvania — 188 chars
- https://weddingnamechange.com/name-change-after-marriage/texas — 183 chars
- https://weddingnamechange.com/name-change-checklist — 200 chars
- https://weddingnamechange.com/passport-photo — 174 chars
notice Legacy image format (jpg/png/gif) with no next-gen fallback
Rule perf.images_legacy_format · Performance · 1 occurrence(s)
- https://weddingnamechange.com/ — 3 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
notice No ETag header (no conditional GET for unchanged pages)
Rule perf.no_etag · Performance · 2 occurrence(s)
- https://weddingnamechange.com/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
- https://weddingnamechange.com/recover — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
notice No Last-Modified header (no conditional GET for unchanged pages)
Rule perf.no_last_modified · Performance · 16 occurrence(s)
- https://weddingnamechange.com/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
- https://weddingnamechange.com/married-name-generator — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
- https://weddingnamechange.com/name-change-after-marriage — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
- https://weddingnamechange.com/name-change-after-marriage/california — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
- https://weddingnamechange.com/name-change-after-marriage/florida — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
- https://weddingnamechange.com/name-change-after-marriage/georgia — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
- https://weddingnamechange.com/name-change-after-marriage/illinois — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
- https://weddingnamechange.com/name-change-after-marriage/michigan — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
- https://weddingnamechange.com/name-change-after-marriage/new-york — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
- https://weddingnamechange.com/name-change-after-marriage/north-carolina — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
- https://weddingnamechange.com/name-change-after-marriage/ohio — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
- https://weddingnamechange.com/name-change-after-marriage/pennsylvania — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
- https://weddingnamechange.com/name-change-after-marriage/texas — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
- https://weddingnamechange.com/name-change-checklist — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
- https://weddingnamechange.com/passport-photo — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
- https://weddingnamechange.com/recover — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
notice Blocked by robots.txt
Rule robots.blocked · Crawlability · 1 occurrence(s)
- https://weddingnamechange.com/legal — Disallowed by robots.txt; not fetched
notice No structured data detected
Rule schema.none · Structured Data · 15 occurrence(s)
- https://weddingnamechange.com/
- https://weddingnamechange.com/married-name-generator
- https://weddingnamechange.com/name-change-after-marriage
- https://weddingnamechange.com/name-change-after-marriage/california
- https://weddingnamechange.com/name-change-after-marriage/florida
- https://weddingnamechange.com/name-change-after-marriage/georgia
- https://weddingnamechange.com/name-change-after-marriage/illinois
- https://weddingnamechange.com/name-change-after-marriage/michigan
- https://weddingnamechange.com/name-change-after-marriage/new-york
- https://weddingnamechange.com/name-change-after-marriage/north-carolina
- https://weddingnamechange.com/name-change-after-marriage/ohio
- https://weddingnamechange.com/name-change-after-marriage/pennsylvania
- https://weddingnamechange.com/name-change-after-marriage/texas
- https://weddingnamechange.com/name-change-checklist
- https://weddingnamechange.com/passport-photo
notice Missing recommended security headers
Rule security.missing_headers · Security · 16 occurrence(s)
- https://weddingnamechange.com/ — CSP
- https://weddingnamechange.com/married-name-generator — CSP
- https://weddingnamechange.com/name-change-after-marriage — CSP
- https://weddingnamechange.com/name-change-after-marriage/california — CSP
- https://weddingnamechange.com/name-change-after-marriage/florida — CSP
- https://weddingnamechange.com/name-change-after-marriage/georgia — CSP
- https://weddingnamechange.com/name-change-after-marriage/illinois — CSP
- https://weddingnamechange.com/name-change-after-marriage/michigan — CSP
- https://weddingnamechange.com/name-change-after-marriage/new-york — CSP
- https://weddingnamechange.com/name-change-after-marriage/north-carolina — CSP
- https://weddingnamechange.com/name-change-after-marriage/ohio — CSP
- https://weddingnamechange.com/name-change-after-marriage/pennsylvania — CSP
- https://weddingnamechange.com/name-change-after-marriage/texas — CSP
- https://weddingnamechange.com/name-change-checklist — CSP
- https://weddingnamechange.com/passport-photo — CSP
- https://weddingnamechange.com/recover — CSP
Pages (showing 17 of 17)
| URL | Status | Indexable | Words | In-links |
|---|---|---|---|---|
| https://weddingnamechange.com/ Wedding Name Change Kit — Pre-filled Forms, Letters & Checklist |
200 | yes | 891 | 16 |
| https://weddingnamechange.com/married-name-generator Married Name Generator — See All Your Last Name Options (Free) · WeddingNameChange.com |
200 | yes | 197 | 16 |
| https://weddingnamechange.com/name-change-after-marriage Name Change After Marriage: State-by-State Guides (2026) · WeddingNameChange.com |
200 | yes | 203 | 16 |
| https://weddingnamechange.com/name-change-after-marriage/california Name Change After Marriage in California (2026): Step-by-Step · WeddingNameChange.com |
200 | yes | 509 | 16 |
| https://weddingnamechange.com/name-change-after-marriage/florida Name Change After Marriage in Florida (2026): Step-by-Step · WeddingNameChange.com |
200 | yes | 503 | 16 |
| https://weddingnamechange.com/name-change-after-marriage/new-york Name Change After Marriage in New York (2026): Step-by-Step · WeddingNameChange.com |
200 | yes | 518 | 16 |
| https://weddingnamechange.com/name-change-after-marriage/pennsylvania Name Change After Marriage in Pennsylvania (2026): Step-by-Step · WeddingNameChange.com |
200 | yes | 494 | 16 |
| https://weddingnamechange.com/name-change-after-marriage/texas Name Change After Marriage in Texas (2026): Step-by-Step · WeddingNameChange.com |
200 | yes | 509 | 16 |
| https://weddingnamechange.com/name-change-checklist Name Change Checklist (2026) — Free & Printable · WeddingNameChange.com |
200 | yes | 318 | 16 |
| https://weddingnamechange.com/passport-photo Free Passport Photo Maker (2x2") — Print Sheet for DS-82 · WeddingNameChange.com |
200 | yes | 227 | 16 |
| https://weddingnamechange.com/recover Recover your kit · WeddingNameChange.com |
200 | no | 138 | 16 |
| https://weddingnamechange.com/name-change-after-marriage/ohio Name Change After Marriage in Ohio (2026): Step-by-Step · WeddingNameChange.com |
200 | yes | 506 | 6 |
| https://weddingnamechange.com/name-change-after-marriage/georgia Name Change After Marriage in Georgia (2026): Step-by-Step · WeddingNameChange.com |
200 | yes | 508 | 1 |
| https://weddingnamechange.com/name-change-after-marriage/illinois Name Change After Marriage in Illinois (2026): Step-by-Step · WeddingNameChange.com |
200 | yes | 505 | 1 |
| https://weddingnamechange.com/name-change-after-marriage/michigan Name Change After Marriage in Michigan (2026): Step-by-Step · WeddingNameChange.com |
200 | yes | 501 | 1 |
| https://weddingnamechange.com/name-change-after-marriage/north-carolina Name Change After Marriage in North Carolina (2026): Step-by-Step · WeddingNameChange.com |
200 | yes | 508 | 1 |
| https://weddingnamechange.com/legal | 0 | no | 0 | 16 |
Audit your own site — free
157 checks, internal PageRank, render-diff. No signup, results in ~30s.