SEO report

SEO report for www.scriptureanalysis.com

https://www.scriptureanalysis.com/ · checked Thu, 05 Nov 2026 07:24 GMT

✓ 25 Passed! 5 Warnings✗ 17 FailedAI readiness 50%Built with WordPress

Fix these first

Your site is built with WordPress. The steps below say where each setting is, and our WordPress SEO guide walks through the rest.

  1. Canonical URLhigh

    No canonical tag.

    Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.

    See the details

  2. Meta descriptionhigh

    No meta description – Google will pick text from the page.

    Fix: Write a 140–155 character description that answers the searcher's question and invites the click.

    On WordPress: Edit the page and scroll to the Yoast SEO or Rank Math box (install one of these free plugins if you have neither), then fill in the meta description.

    See the details

  3. Entity clarityhigh

    No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.

    Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.

    See the details

  4. JSON-LD present & validhigh

    No JSON-LD structured data.

    Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).

    See the details

  5. Render-blocking resourceshigh

    3 blocking script(s) and 5 stylesheet(s) in <head>.

    Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.

    See the details

  6. Title tagcritical

    “Scripture Analysis – Scripture and textual criticism resources”

    Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.

    On WordPress: Edit the page and scroll to the Yoast SEO or Rank Math box (install one of these free plugins if you have neither), then fill in the SEO title.

    See the details

  7. HTTPScritical

    5 file(s) load over insecure http:// (mixed content) – browsers may block them.

    Fix: Serve everything over HTTPS and update http:// file links.

    On WordPress: Ask your host to turn on a free SSL certificate, then in Settings → General change both addresses to start with https://.

    See the details

  8. Open Graph & social cardsmedium

    Open Graph title or image missing.

    Fix: Add og:title, og:description, og:image (1200×630 PNG/JPG, absolute URL) and twitter:card=summary_large_image.

    On WordPress: Yoast SEO and Rank Math add these tags for you. Set a sharing image in the plugin's Social tab on each page.

    See the details

Check the whole website

This report covers one page. The full-site audit crawls up to 250 pages to find broken links, duplicate titles, orphan pages and more.

Run a full-site audit

Monitor this site weekly

We'll re-check it every week and track the score, with a history graph and a list of anything that breaks.

Compare with competitors

See how this page scores against up to two competitors, side by side, and where they beat you.

Compare sites

Real-world speed Google PageSpeed

Loading Core Web Vitals from Google… this can take up to 30 seconds.

Authority & backlinks

Looking up which websites link to scriptureanalysis.com…

Indexing & crawling 88%

Can search engines reach, read and index this page?

  • ✓

    Status codecritical

    The page returned HTTP 200.

  • ✓

    Indexablecritical

    No noindex instruction – the page can appear in search.

  • ✓

    robots.txthigh

    robots.txt found.

    Googlebot is allowed to crawl this page.

  • ✓

    XML sitemaphigh

    Sitemap index found at https://www.scriptureanalysis.com/wp-sitemap.xml listing 5 sitemaps.

    Declared in robots.txt.

    No lastmod dates – add accurate ones so search engines know what changed.

  • ✗

    Canonical URLhigh

    No canonical tag.

    Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.

  • ✓

    Redirectshigh

    1 redirect before the page loaded.

    https://scriptureanalysis.com/ → https://www.scriptureanalysis.com/

    A single redirect to your preferred address is normal; just make sure your own links use the final address.

  • ✓

    www / non-wwwmedium

    scriptureanalysis.com redirects to www.scriptureanalysis.com.

Search snippet & sharing 29%

How the page looks in Google results and when shared.

  • !

    Title tagcritical

    “Scripture Analysis – Scripture and textual criticism resources”

    About 537px of Google's ~580px desktop width.

    Repeated words: scripture.

    Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.

    On WordPress: Edit the page and scroll to the Yoast SEO or Rank Math box (install one of these free plugins if you have neither), then fill in the SEO title.

  • ✗

    Meta descriptionhigh

    No meta description – Google will pick text from the page.

    Fix: Write a 140–155 character description that answers the searcher's question and invites the click.

    On WordPress: Edit the page and scroll to the Yoast SEO or Rank Math box (install one of these free plugins if you have neither), then fill in the meta description.

  • ✗

    Open Graph & social cardsmedium

    Open Graph title or image missing.

    No twitter:card tag.

    Fix: Add og:title, og:description, og:image (1200×630 PNG/JPG, absolute URL) and twitter:card=summary_large_image.

    On WordPress: Yoast SEO and Rank Math add these tags for you. Set a sharing image in the plugin's Social tab on each page.

  • ✗

    Faviconlow

    No favicon linked.

    Fix: Add a square favicon at least 48×48px.

    On WordPress: Appearance → Customize → Site Identity → Site Icon (Settings → General in newer versions).

  • ✓

    Languagelow

    lang="en-US"

Content quality 100%

Is there enough clear, useful text that matches what the page targets?

  • ✓

    Word countmedium

    728 words of main content (inside <main>).

    Google has no minimum word count – this is a rough guide to whether the page answers the question in full.

  • ✓

    Readabilitymedium

    Flesch reading ease 50 (fairly easy), about 14 words per sentence.

  • ✓

    Topic focushigh

    5 of 5 title keywords appear in the main content.

  • ✓

    H1 headingcritical

    “Scripture Analysis”

  • ✓

    Heading structuremedium

    18 headings for 728 words.

    Levels are in order.

  • ✓

    Text-to-code ratiolow

    10% of the HTML is visible text.

AI search readiness 50%

Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?

  • ✓

    AI crawler accesshigh

    Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.

  • ✓

    Snippet controlshigh

    No snippet restrictions – search and AI answers can quote this page.

  • ✗

    llms.txtlow

    No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.

    Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.

  • ✗

    Question-led contentmedium

    No headings phrased as questions.

    Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.

  • ✗

    Entity clarityhigh

    No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.

    Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.

  • ✓

    Freshness signalsmedium

    The page shows when it was published or last updated.

  • ✗

    Trust pages (E-E-A-T)medium

    No links found to about, contact or privacy pages.

    Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.

Structured data 0%

Machine-readable facts for rich results and AI.

Performance 56%

Speed signals from the HTML and server. Real-user Core Web Vitals load below.

  • ✓

    Server response (TTFB)high

    673 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).

  • ✓

    HTML sizemedium

    119 kB of HTML.

  • ✓

    Compressionmedium

    Compressed with br.

  • ✗

    Render-blocking resourceshigh

    3 blocking script(s) and 5 stylesheet(s) in <head>.

    Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.

  • !

    Scripts & third partiesmedium

    11 script tag(s); files loaded from 2 other domain(s): fonts.googleapis.com, maps.google.com.

    Fix: Remove unused tracking and widget scripts; every third party adds connection time.

  • ✗

    Imagesmedium

    16 image(s).

    6 without width/height – can cause layout shift (CLS).

    6 image(s) after the first three aren't lazy-loaded.

    10 use WebP/AVIF or responsive srcset.

    Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.

    On WordPress: Install a free image optimiser plugin (such as EWWW Image Optimizer or Smush) to shrink images and serve WebP.

  • ✗

    Cachinglow

    No Cache-Control header.

    Fix: Set Cache-Control so browsers and CDNs can reuse the page.

  • ✓

    HTTP/3low

    Server advertises HTTP/3 (faster on mobile networks).

Security 46%

Visitor safety signals that browsers and Google check.

  • !

    HTTPScritical

    5 file(s) load over insecure http:// (mixed content) – browsers may block them.

    Fix: Serve everything over HTTPS and update http:// file links.

    On WordPress: Ask your host to turn on a free SSL certificate, then in Settings → General change both addresses to start with https://.

  • ✓

    HTTP → HTTPS redirecthigh

    http:// redirects to https://.

  • ✗

    HSTSmedium

    No Strict-Transport-Security header.

    Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.

  • ✗

    Security headerslow

    Present: CSP.

    Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).

  • ✗

    Server fingerprintlow

    X-Powered-By reveals “PHP/8.4.27”.

    Fix: Remove X-Powered-By so attackers can't see your software versions.

Mobile & accessibility 60%

Usable on phones and by everyone – Google indexes the mobile version.

  • ✓

    Mobile viewportcritical

    viewport: width=device-width, initial-scale=1

  • ✗

    Image alt textmedium

    5 of 16 images have no alt attribute.

    Fix: Describe each meaningful image in its alt attribute (use alt="" for decorative ones).

    On WordPress: Media → Library: click each image and fill in Alternative Text. For images already on a page, select the image block and fill in Alternative text in the sidebar.

  • ✗

    Tap-to-contactmedium

    No tel: or mailto: links.

    Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.

Local SEO not scored

This site doesn't look like a local business, so these checks are shown for information and not scored.

  • i

    LocalBusiness markuphigh

    No LocalBusiness structured data.

  • i

    Contact details on pagemedium

    No phone number found.

    No postcode found (fine for service-area businesses).

  • i

    Map & directionslow

    No map or directions link.

This report checks one page. Scores are a guide, not a guarantee of rankings. Check another page · Print or save as PDF

Want these fixed for you? XKey is made by IceWork, a Blackpool web studio. IceWork builds fast websites that pass every check here – a 3-page site with domain and a year's hosting is £350 all in.