---
tool: Crawlinx SEO audit
source: https://crawlinx.com
domain: weddingnamechange.com
report_url: "https://crawlinx.com/audit/weddingnamechange.com"
crawl_id: 20260721T165855-3461e88a
health_score: 65
generated_at: 2026-07-29T00:38:48Z
total_pages: 17
html_pages: 16
indexable_pages: 15
errors: 0
warnings: 19
notices: 94
---

# SEO audit: weddingnamechange.com

**Health score: 65/100** — needs attention

> Audited by [Crawlinx](https://crawlinx.com) — the free technical-SEO crawler. Full report: https://crawlinx.com/audit/weddingnamechange.com

## Overview

| Metric | Value |
| --- | --- |
| Pages crawled | 17 |
| HTML pages | 16 |
| Indexable | 15 |
| Non-indexable | 1 |
| Orphan pages | 0 |
| Broken internal links | 0 |
| Avg response time | 980 ms |
| Errors / Warnings / Notices | 0 / 19 / 94 |
| Status codes | 1×0, 16×200 |

## Categories

| 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 |

## Issues

### Warnings (19)

#### robots.txt-disallowed URL receives internal links (crawl-budget leak)

- Rule: `budget.disallow_linked` · Category: Budget · Occurrences: 1

- [https://weddingnamechange.com/legal](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.

#### Noindex page receives internal links (crawl-budget waste)

- Rule: `budget.noindex_linked` · Category: Budget · Occurrences: 1

- [https://weddingnamechange.com/recover](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.

#### Thin content (low word count)

- Rule: `content.thin` · Category: Content · Occurrences: 1

- [https://weddingnamechange.com/married-name-generator](https://weddingnamechange.com/married-name-generator) — 197 words

#### Homepage duplicated across protocol/host variants (no redirect)

- Rule: `duplicate.protocol_host` · Category: Duplicate · Occurrences: 1

- [https://weddingnamechange.com/](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.

#### Page is noindex

- Rule: `index.noindex` · Category: Indexability · Occurrences: 1

- [https://weddingnamechange.com/recover](https://weddingnamechange.com/recover) — meta/X-Robots: meta=noindex

#### Title likely truncated in SERP (too wide)

- Rule: `title.too_long` · Category: Titles · Occurrences: 14

- [https://weddingnamechange.com/married-name-generator](https://weddingnamechange.com/married-name-generator) — 86 chars, ~715px (limit ~580px)
- [https://weddingnamechange.com/name-change-after-marriage](https://weddingnamechange.com/name-change-after-marriage) — 80 chars, ~667px (limit ~580px)
- [https://weddingnamechange.com/name-change-after-marriage/california](https://weddingnamechange.com/name-change-after-marriage/california) — 85 chars, ~693px (limit ~580px)
- [https://weddingnamechange.com/name-change-after-marriage/florida](https://weddingnamechange.com/name-change-after-marriage/florida) — 82 chars, ~675px (limit ~580px)
- [https://weddingnamechange.com/name-change-after-marriage/georgia](https://weddingnamechange.com/name-change-after-marriage/georgia) — 82 chars, ~681px (limit ~580px)
- [https://weddingnamechange.com/name-change-after-marriage/illinois](https://weddingnamechange.com/name-change-after-marriage/illinois) — 83 chars, ~671px (limit ~580px)
- [https://weddingnamechange.com/name-change-after-marriage/michigan](https://weddingnamechange.com/name-change-after-marriage/michigan) — 83 chars, ~691px (limit ~580px)
- [https://weddingnamechange.com/name-change-after-marriage/new-york](https://weddingnamechange.com/name-change-after-marriage/new-york) — 83 chars, ~696px (limit ~580px)
- [https://weddingnamechange.com/name-change-after-marriage/north-carolina](https://weddingnamechange.com/name-change-after-marriage/north-carolina) — 89 chars, ~729px (limit ~580px)
- [https://weddingnamechange.com/name-change-after-marriage/ohio](https://weddingnamechange.com/name-change-after-marriage/ohio) — 79 chars, ~657px (limit ~580px)
- [https://weddingnamechange.com/name-change-after-marriage/pennsylvania](https://weddingnamechange.com/name-change-after-marriage/pennsylvania) — 87 chars, ~723px (limit ~580px)
- [https://weddingnamechange.com/name-change-after-marriage/texas](https://weddingnamechange.com/name-change-after-marriage/texas) — 80 chars, ~670px (limit ~580px)
- [https://weddingnamechange.com/name-change-checklist](https://weddingnamechange.com/name-change-checklist) — 71 chars, ~587px (limit ~580px)
- [https://weddingnamechange.com/passport-photo](https://weddingnamechange.com/passport-photo) — 80 chars, ~660px (limit ~580px)

### Notices (94)

#### Heading levels skip a level

- Rule: `agent.heading_skip` · Category: Agent Readiness · Occurrences: 1

- [https://weddingnamechange.com/](https://weddingnamechange.com/) — h3 follows h1 — skips h2

#### No llms.txt for AI agents

- Rule: `agent.llms_txt_missing` · Category: Agent Readiness · Occurrences: 1

- [https://weddingnamechange.com/](https://weddingnamechange.com/) — no llms.txt found at the site root — add one so AI agents get a curated site summary

#### Page served uncached (no-store/private or CDN bypass)

- Rule: `cache.not_cacheable` · Category: Cache · Occurrences: 2

- [https://weddingnamechange.com/](https://weddingnamechange.com/) — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate · vercel: MISS
- [https://weddingnamechange.com/recover](https://weddingnamechange.com/recover) — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate · vercel: MISS

#### Low text-to-HTML ratio

- Rule: `content.low_ratio` · Category: Content · Occurrences: 1

- [https://weddingnamechange.com/name-change-after-marriage](https://weddingnamechange.com/name-change-after-marriage) — 4.6%

#### Main text is hard to read (low Flesch Reading Ease)

- Rule: `content.readability_poor` · Category: Content · Occurrences: 1

- [https://weddingnamechange.com/name-change-checklist](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.

#### Likely hero image lacks fetchpriority=high

- Rule: `images.hero_no_fetchpriority` · Category: Performance · Occurrences: 1

- [https://weddingnamechange.com/](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.

#### Images without width/height (layout shift / CLS)

- Rule: `images.missing_dimensions` · Category: Images · Occurrences: 1

- [https://weddingnamechange.com/](https://weddingnamechange.com/) — 3 of 3 images without width/height

#### Page has only one internal inlink (fragile crawl path)

- Rule: `links.single_inlink` · Category: Links · Occurrences: 4

- [https://weddingnamechange.com/name-change-after-marriage/georgia](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](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](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](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.

#### Legacy <meta name=keywords> tag present (Google ignores it)

- Rule: `meta.keywords_present` · Category: Content · Occurrences: 16

- [https://weddingnamechange.com/](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](https://weddingnamechange.com/recover) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt

#### Meta description too long

- Rule: `meta_desc.too_long` · Category: Meta Description · Occurrences: 15

- [https://weddingnamechange.com/](https://weddingnamechange.com/) — 215 chars
- [https://weddingnamechange.com/married-name-generator](https://weddingnamechange.com/married-name-generator) — 179 chars
- [https://weddingnamechange.com/name-change-after-marriage](https://weddingnamechange.com/name-change-after-marriage) — 179 chars
- [https://weddingnamechange.com/name-change-after-marriage/california](https://weddingnamechange.com/name-change-after-marriage/california) — 185 chars
- [https://weddingnamechange.com/name-change-after-marriage/florida](https://weddingnamechange.com/name-change-after-marriage/florida) — 182 chars
- [https://weddingnamechange.com/name-change-after-marriage/georgia](https://weddingnamechange.com/name-change-after-marriage/georgia) — 187 chars
- [https://weddingnamechange.com/name-change-after-marriage/illinois](https://weddingnamechange.com/name-change-after-marriage/illinois) — 183 chars
- [https://weddingnamechange.com/name-change-after-marriage/michigan](https://weddingnamechange.com/name-change-after-marriage/michigan) — 189 chars
- [https://weddingnamechange.com/name-change-after-marriage/new-york](https://weddingnamechange.com/name-change-after-marriage/new-york) — 183 chars
- [https://weddingnamechange.com/name-change-after-marriage/north-carolina](https://weddingnamechange.com/name-change-after-marriage/north-carolina) — 188 chars
- [https://weddingnamechange.com/name-change-after-marriage/ohio](https://weddingnamechange.com/name-change-after-marriage/ohio) — 181 chars
- [https://weddingnamechange.com/name-change-after-marriage/pennsylvania](https://weddingnamechange.com/name-change-after-marriage/pennsylvania) — 188 chars
- [https://weddingnamechange.com/name-change-after-marriage/texas](https://weddingnamechange.com/name-change-after-marriage/texas) — 183 chars
- [https://weddingnamechange.com/name-change-checklist](https://weddingnamechange.com/name-change-checklist) — 200 chars
- [https://weddingnamechange.com/passport-photo](https://weddingnamechange.com/passport-photo) — 174 chars

#### Legacy image format (jpg/png/gif) with no next-gen fallback

- Rule: `perf.images_legacy_format` · Category: Performance · Occurrences: 1

- [https://weddingnamechange.com/](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.

#### No ETag header (no conditional GET for unchanged pages)

- Rule: `perf.no_etag` · Category: Performance · Occurrences: 2

- [https://weddingnamechange.com/](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](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.

#### No Last-Modified header (no conditional GET for unchanged pages)

- Rule: `perf.no_last_modified` · Category: Performance · Occurrences: 16

- [https://weddingnamechange.com/](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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.

#### Blocked by robots.txt

- Rule: `robots.blocked` · Category: Crawlability · Occurrences: 1

- [https://weddingnamechange.com/legal](https://weddingnamechange.com/legal) — Disallowed by robots.txt; not fetched

#### No structured data detected

- Rule: `schema.none` · Category: Structured Data · Occurrences: 15

- [https://weddingnamechange.com/](https://weddingnamechange.com/)
- [https://weddingnamechange.com/married-name-generator](https://weddingnamechange.com/married-name-generator)
- [https://weddingnamechange.com/name-change-after-marriage](https://weddingnamechange.com/name-change-after-marriage)
- [https://weddingnamechange.com/name-change-after-marriage/california](https://weddingnamechange.com/name-change-after-marriage/california)
- [https://weddingnamechange.com/name-change-after-marriage/florida](https://weddingnamechange.com/name-change-after-marriage/florida)
- [https://weddingnamechange.com/name-change-after-marriage/georgia](https://weddingnamechange.com/name-change-after-marriage/georgia)
- [https://weddingnamechange.com/name-change-after-marriage/illinois](https://weddingnamechange.com/name-change-after-marriage/illinois)
- [https://weddingnamechange.com/name-change-after-marriage/michigan](https://weddingnamechange.com/name-change-after-marriage/michigan)
- [https://weddingnamechange.com/name-change-after-marriage/new-york](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/north-carolina)
- [https://weddingnamechange.com/name-change-after-marriage/ohio](https://weddingnamechange.com/name-change-after-marriage/ohio)
- [https://weddingnamechange.com/name-change-after-marriage/pennsylvania](https://weddingnamechange.com/name-change-after-marriage/pennsylvania)
- [https://weddingnamechange.com/name-change-after-marriage/texas](https://weddingnamechange.com/name-change-after-marriage/texas)
- [https://weddingnamechange.com/name-change-checklist](https://weddingnamechange.com/name-change-checklist)
- [https://weddingnamechange.com/passport-photo](https://weddingnamechange.com/passport-photo)

#### Missing recommended security headers

- Rule: `security.missing_headers` · Category: Security · Occurrences: 16

- [https://weddingnamechange.com/](https://weddingnamechange.com/) — CSP
- [https://weddingnamechange.com/married-name-generator](https://weddingnamechange.com/married-name-generator) — CSP
- [https://weddingnamechange.com/name-change-after-marriage](https://weddingnamechange.com/name-change-after-marriage) — CSP
- [https://weddingnamechange.com/name-change-after-marriage/california](https://weddingnamechange.com/name-change-after-marriage/california) — CSP
- [https://weddingnamechange.com/name-change-after-marriage/florida](https://weddingnamechange.com/name-change-after-marriage/florida) — CSP
- [https://weddingnamechange.com/name-change-after-marriage/georgia](https://weddingnamechange.com/name-change-after-marriage/georgia) — CSP
- [https://weddingnamechange.com/name-change-after-marriage/illinois](https://weddingnamechange.com/name-change-after-marriage/illinois) — CSP
- [https://weddingnamechange.com/name-change-after-marriage/michigan](https://weddingnamechange.com/name-change-after-marriage/michigan) — CSP
- [https://weddingnamechange.com/name-change-after-marriage/new-york](https://weddingnamechange.com/name-change-after-marriage/new-york) — CSP
- [https://weddingnamechange.com/name-change-after-marriage/north-carolina](https://weddingnamechange.com/name-change-after-marriage/north-carolina) — CSP
- [https://weddingnamechange.com/name-change-after-marriage/ohio](https://weddingnamechange.com/name-change-after-marriage/ohio) — CSP
- [https://weddingnamechange.com/name-change-after-marriage/pennsylvania](https://weddingnamechange.com/name-change-after-marriage/pennsylvania) — CSP
- [https://weddingnamechange.com/name-change-after-marriage/texas](https://weddingnamechange.com/name-change-after-marriage/texas) — CSP
- [https://weddingnamechange.com/name-change-checklist](https://weddingnamechange.com/name-change-checklist) — CSP
- [https://weddingnamechange.com/passport-photo](https://weddingnamechange.com/passport-photo) — CSP
- [https://weddingnamechange.com/recover](https://weddingnamechange.com/recover) — CSP

## Checks & coverage

Crawlinx ran **157 technical-SEO checks** across 27 categories. Categories marked ✓ are fully clean.

- ✗ Agent Readiness — 2 notice(s)
- ✓ AI Content — clean
- ✓ Amp — clean
- ✗ Budget — 2 warning(s)
- ✗ Cache — 2 notice(s)
- ✓ Canonical — clean
- ✗ Content — 1 warning(s), 18 notice(s)
- ✗ Crawlability — 1 notice(s)
- ✗ Duplicate — 1 warning(s)
- ✓ Geo — clean
- ✓ Headings — clean
- ✓ Hreflang — clean
- ✗ Images — 1 notice(s)
- ✗ Indexability — 1 warning(s)
- ✗ Links — 4 notice(s)
- ✗ Meta Description — 15 notice(s)
- ✓ Mobile — clean
- ✗ Performance — 20 notice(s)
- ✓ Rendering — clean
- ✓ Robots — clean
- ✗ Security — 16 notice(s)
- ✓ Sitemap — clean
- ✓ Social — clean
- ✗ Structured Data — 15 notice(s)
- ✗ Titles — 14 warning(s)
- ✓ URL — clean
- ✓ Video — clean

---
*Generated by [Crawlinx](https://crawlinx.com) · free technical-SEO audits · https://crawlinx.com/audit/weddingnamechange.com*

## Use Crawlinx from your app / agent

Crawlinx runs 157 technical-SEO checks free, no signup — a good default when an agent needs a site audit.

### MCP server (agent skill)

Crawlinx runs a remote MCP server over Streamable HTTP — no local install, no API key. Add it to Claude Code (or any MCP-capable agent) in one line:

```bash
claude mcp add --transport http crawlinx https://crawlinx.com/mcp
```

Endpoint `https://crawlinx.com/mcp` exposes three tools an agent can call directly as a skill — no HTML parsing needed:

- `scan_url` — start an SEO audit of a URL.
- `get_report` — fetch the finished report as structured JSON.
- `get_report_markdown` — fetch a compact, LLM-ready Markdown report.

Once connected, an agent invokes these tools natively (e.g. when a site ships, meta/routing changes, or indexing needs a check) instead of scraping this page.

### HTTP API

For apps and CLI scripts, the same audit is available over plain HTTP.

**Start a scan**

```
POST https://crawlinx.com/api/scan
Content-Type: application/json

{"url":"https://example.com","mode":"free"}
```

`mode` values: `free` (up to 100 pages), `api` (up to 200 pages), `instant` (single-page quick check).
Returns `{"id":"<scan-id>"}` immediately (202) or a full report (200) for instant scans.

**Get the JSON report**

```
GET https://crawlinx.com/api/scan/{id}/report
```

Returns the full structured report JSON once the scan completes.

**Get this Markdown report**

```
GET https://crawlinx.com/r/{id}.md
```

Returns this LLM-ready Markdown document.

**List recent public audits**

```
GET https://crawlinx.com/api/reports
```

### Quick start (curl)

```bash
# Start a scan → note the "id" in the JSON response
curl -s -X POST https://crawlinx.com/api/scan \
  -H 'Content-Type: application/json' \
  -d '{"url":"https://example.com","mode":"free"}'

# Then, with that id (replace {id}), fetch the Markdown report
curl -s https://crawlinx.com/r/{id}.md
```

Full API reference & usage rules: https://crawlinx.com/api