Catalog / 4gengenealogy.com
74

SEO audit for 4gengenealogy.com

FOUR GENERATIONS GENEALOGY - Home

other

Health 74/100 (fair) · 20 pages crawled · generated 2026-08-26

Download Markdown report (feed to ChatGPT / Claude / Cursor)

J. H. ("Jay") Fonkert, CG

Screenshot of 4gengenealogy.com
20
pages crawled
14
indexable pages
0
errors
89
warnings
163
notices
1
orphan pages
0
broken links
Category breakdown
CategoryScoreErrorsWarningsNotices
Links 78 0 15 0
Canonical 79 0 14 0
Headings 79 0 14 0
Performance 79 0 14 35
Duplicate 82 0 12 11
Agent Readiness 90 0 7 15
Images 90 0 7 12
Content 91 0 6 12
Cache 100 0 0 14
Crawlability 100 0 0 1
Meta Description 100 0 0 12
Security 100 0 0 14
Sitemap 100 0 0 4
Social 100 0 0 14
Structured Data 100 0 0 14
URL 100 0 0 5
Findings

Warnings (11 rules)

warning Control has no accessible name

Rule agent.control_no_name · Agent Readiness · 7 occurrence(s)

warning Duplicate page content

Rule duplicate.content · Duplicate · 2 occurrence(s)

warning Near-duplicate page content

Rule duplicate.near · Duplicate · 2 occurrence(s)

warning Duplicate <title> across pages

Rule duplicate.title · Duplicate · 8 occurrence(s)

warning Orphan page (no internal inlinks)

Rule links.orphan · Links · 1 occurrence(s)

warning Internal link points to a redirect

Rule links.redirect_target · Links · 14 occurrence(s)

warning Render-blocking script in <head> (no defer/async)

Rule perf.render_blocking · Performance · 14 occurrence(s)

Notices (20 rules)

notice No llms.txt for AI agents

Rule agent.llms_txt_missing · Agent Readiness · 1 occurrence(s)

notice No main landmark for AI agents

Rule agent.no_main_landmark · Agent Readiness · 14 occurrence(s)

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

Rule cache.not_cacheable · Cache · 14 occurrence(s)

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

Rule content.readability_poor · Content · 5 occurrence(s)

  • https://www.4gengenealogy.com/ — this page reads as difficult (Flesch Reading Ease 35, 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.
  • https://www.4gengenealogy.com/about-me.html — this page reads as very difficult (Flesch Reading Ease 4, 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.
  • https://www.4gengenealogy.com/index.html — this page reads as difficult (Flesch Reading Ease 35, 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.
  • https://www.4gengenealogy.com/publications.html — this page reads as difficult (Flesch Reading Ease 31, 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.
  • https://www.4gengenealogy.com/services.html — this page reads as very difficult (Flesch Reading Ease 17, 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 Duplicate meta description across pages

Rule duplicate.meta_desc · Duplicate · 11 occurrence(s)

notice Image filename is generic/auto-generated (missed image-search signal)

Rule images.generic_filename · Images · 2 occurrence(s)

  • https://www.4gengenealogy.com/ — 1 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
  • https://www.4gengenealogy.com/index.html — 1 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.

notice Likely hero image lacks fetchpriority=high

Rule images.hero_no_fetchpriority · Performance · 10 occurrence(s)

  • https://www.4gengenealogy.com/ — the likely hero/LCP image (dsc06212.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.
  • https://www.4gengenealogy.com/about-me.html — the likely hero/LCP image (certified-bcg-logo-certified-600x663.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.
  • https://www.4gengenealogy.com/fonkgenbloggings.html — the likely hero/LCP image (bg_feed.gif) 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.
  • https://www.4gengenealogy.com/fonkgenbloggings/archives/08-2022 — the likely hero/LCP image (bg_feed.gif) 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.
  • https://www.4gengenealogy.com/fonkgenbloggings/archives/09-2022 — the likely hero/LCP image (bg_feed.gif) 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.
  • https://www.4gengenealogy.com/fonkgenbloggings/category/all — the likely hero/LCP image (bg_feed.gif) 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.
  • https://www.4gengenealogy.com/fonkgenbloggings/kate-aka-trijntje-from-terschelling — the likely hero/LCP image (bg_feed.gif) 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.
  • https://www.4gengenealogy.com/fonkgenbloggings/new-blogginnings — the likely hero/LCP image (bg_feed.gif) 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.
  • https://www.4gengenealogy.com/fonkgenbloggings/sipke-zorgdrager-tot-verbetering-van-bestaan — the likely hero/LCP image (bg_feed.gif) 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.
  • https://www.4gengenealogy.com/index.html — the likely hero/LCP image (dsc06212.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 · 10 occurrence(s)

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

Rule meta.keywords_present · Content · 7 occurrence(s)

notice Meta description too short

Rule meta_desc.too_short · Meta Description · 6 occurrence(s)

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

Rule perf.images_legacy_format · Performance · 10 occurrence(s)

notice Large HTML document

Rule perf.large_html · Performance · 1 occurrence(s)

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

Rule perf.no_etag · Performance · 14 occurrence(s)

  • https://www.4gengenealogy.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://www.4gengenealogy.com/about-me.html — 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://www.4gengenealogy.com/fonkgenbloggings.html — 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://www.4gengenealogy.com/fonkgenbloggings/archives/08-2022 — 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://www.4gengenealogy.com/fonkgenbloggings/archives/09-2022 — 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://www.4gengenealogy.com/fonkgenbloggings/category/all — 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://www.4gengenealogy.com/fonkgenbloggings/kate-aka-trijntje-from-terschelling — 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://www.4gengenealogy.com/fonkgenbloggings/new-blogginnings — 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://www.4gengenealogy.com/fonkgenbloggings/sipke-zorgdrager-tot-verbetering-van-bestaan — 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://www.4gengenealogy.com/index.html — 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://www.4gengenealogy.com/lectures-and-classes.html — 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://www.4gengenealogy.com/my-family-history.html — 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://www.4gengenealogy.com/publications.html — 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://www.4gengenealogy.com/services.html — 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 URL redirects to another URL

Rule redirect.single · Crawlability · 1 occurrence(s)

notice Missing recommended security headers

Rule security.missing_headers · Security · 14 occurrence(s)

notice Indexable page not listed in sitemap

Rule sitemap.orphan_not_listed · Sitemap · 4 occurrence(s)

Pages (showing 20 of 20)
URLStatusIndexableWordsIn-links
https://www.4gengenealogy.com/
FOUR GENERATIONS GENEALOGY - Home
200 yes 109 14
https://www.4gengenealogy.com/about-me.html
About Me - FOUR GENERATIONS GENEALOGY
200 yes 168 14
https://www.4gengenealogy.com/fonkgenbloggings.html
FOUR GENERATIONS GENEALOGY - FonkGen Bloggings
200 yes 1681 14
https://www.4gengenealogy.com/lectures-and-classes.html
Lectures and Classes - FOUR GENERATIONS GENEALOGY
200 yes 87 14
https://www.4gengenealogy.com/my-family-history.html
My Family History - FOUR GENERATIONS GENEALOGY
200 yes 255 14
https://www.4gengenealogy.com/publications.html
Publications - FOUR GENERATIONS GENEALOGY
200 yes 122 14
https://www.4gengenealogy.com/services.html
Services - FOUR GENERATIONS GENEALOGY
200 yes 112 14
https://www.4gengenealogy.com/fonkgenbloggings/archives/08-2022
FonkGen Bloggings - FOUR GENERATIONS GENEALOGY
200 yes 387 7
https://www.4gengenealogy.com/fonkgenbloggings/archives/09-2022
FonkGen Bloggings - FOUR GENERATIONS GENEALOGY
200 yes 1358 7
https://www.4gengenealogy.com/fonkgenbloggings/category/all
FonkGen Bloggings - FOUR GENERATIONS GENEALOGY
200 yes 1681 7
https://www.4gengenealogy.com/fonkgenbloggings/new-blogginnings
FonkGen Bloggings - FOUR GENERATIONS GENEALOGY
200 yes 417 4
https://www.4gengenealogy.com/fonkgenbloggings/kate-aka-trijntje-from-terschelling
FonkGen Bloggings - FOUR GENERATIONS GENEALOGY
200 yes 706 4
https://www.4gengenealogy.com/fonkgenbloggings/sipke-zorgdrager-tot-verbetering-van-bestaan
FonkGen Bloggings - FOUR GENERATIONS GENEALOGY
200 yes 722 4
https://www.4gengenealogy.com/index.html
FOUR GENERATIONS GENEALOGY - Home
200 yes 109 0
https://www.4gengenealogy.com/2/feed 200 no 0 7
https://www.4gengenealogy.com/uploads/1/3/7/0/137005420/descendants_of__adriaen_willemsz_fonckert_of_rhoon.pdf 200 no 0 1
https://www.4gengenealogy.com/uploads/1/3/7/0/137005420/fonkert_genealogy_publications_for_website_19aug2022.pdf 200 no 0 1
https://www.4gengenealogy.com/uploads/1/3/7/0/137005420/fonkert_lecture_offerings_modified_august_2022.pdf 200 no 0 1
https://www.4gengenealogy.com/uploads/1/3/7/0/137005420/fonkert_lecture_offerings_modified_feb_2026.pdf 200 no 0 1
https://www.4gengenealogy.com/uploads/1/3/7/0/137005420/the_klaaswaal_fonkerts_2022_condensed_2sep2022.pdf 200 no 0 1

Audit your own site — free

157 checks, internal PageRank, render-diff. No signup, results in ~30s.

Scan your site →