SEO report

SEO report for www.tomsguide.com

https://www.tomsguide.com/ · checked Sun, 01 Nov 2026 16:05 GMT

✓ 32 Passed! 4 Warnings✗ 11 FailedAI readiness 47%

Fix these first

  1. H1 headingcritical

    No H1 heading.

    Fix: Use one H1 that states the page topic with its main keyword.

    See the details

  2. Internal linkinghigh

    0 internal and 0 external links.

    Fix: Link to your most important pages from this page with descriptive text.

    See the details

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

    See the details

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

    See the details

  5. Freshness signalsmedium

    No published/updated date found.

    Fix: Show a 'last updated' date and add dateModified to your structured data.

    See the details

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

    See the details

  7. HTML sizemedium

    978 kB of HTML – heavy for phones (we only analysed the first 1 MB).

    Fix: Remove inline bloat, base64 images and unused markup.

    See the details

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

    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 tomsguide.com…

Indexing & crawling 100%

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.tomsguide.com/sitemap.xml listing 190 sitemaps.

    Declared in robots.txt.

    Most recent lastmod: 2026-11-01T14:00:00Z.

  • ✓

    Canonical URLhigh

    Canonical: https://www.tomsguide.com

    Points to this page (self-referencing).

  • ✓

    Redirectshigh

    1 redirect before the page loaded.

    https://tomsguide.com/ → https://www.tomsguide.com/

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

  • ✓

    www / non-wwwmedium

    tomsguide.com redirects to www.tomsguide.com.

  • ✓

    hreflangmedium

    6 hreflang link(s).

    All language codes are valid.

Search snippet & sharing 71%

How the page looks in Google results and when shared.

Content quality 46%

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

  • ✓

    Word countmedium

    405 words of main content (menus and footer excluded).

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

  • i

    Readabilitymedium

    Not enough paragraph text to score readability.

  • ✓

    Topic focushigh

    7 of 7 title keywords appear in the main content.

  • ✗

    H1 headingcritical

    No H1 heading.

    Fix: Use one H1 that states the page topic with its main keyword.

  • !

    Heading structuremedium

    0 headings for 405 words.

    Levels are in order.

    Fix: Use H2s for main sections and H3s inside them, without skipping levels.

  • ✗

    Text-to-code ratiolow

    1% of the HTML is visible text.

    Fix: Trim unused markup, inline scripts and builder bloat.

AI search readiness 47%

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

  • !

    AI crawler accesshigh

    robots.txt blocks search crawlers: Applebot (Siri & Spotlight).

    Training-only crawlers blocked: Applebot-Extended, meta-externalagent. That's a licensing choice – these companies document them as separate from their search crawlers.

    Fix: Allow Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot and PerplexityBot so search and AI tools can cite you (you can still block training-only bots such as GPTBot or Google-Extended).

  • ✓

    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

    Identified as: Organization, Person.

    8 official profile link(s) (sameAs).

  • ✗

    Freshness signalsmedium

    No published/updated date found.

    Fix: Show a 'last updated' date and add dateModified to your structured data.

  • ✗

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

Machine-readable facts for rich results and AI.

  • ✓

    JSON-LD present & validhigh

    4 JSON-LD block(s): WebPage, WebSite, Organization, ImageObject, Person, Place, PostalAddress, SearchAction, SiteNavigationElement, ItemList.

    All blocks parse correctly.

  • ✓

    Required propertiesmedium

    Key types include Google's required properties.

  • i

    Breadcrumbslow

    Home page – breadcrumbs not needed.

Performance 84%

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

  • ✓

    Server response (TTFB)high

    26 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

    978 kB of HTML – heavy for phones (we only analysed the first 1 MB).

    Fix: Remove inline bloat, base64 images and unused markup.

  • ✓

    Compressionmedium

    Compressed with br.

  • ✓

    Render-blocking resourceshigh

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

  • ✓

    Scripts & third partiesmedium

    1 script tag(s); files loaded from 2 other domain(s): cdn.mos.cms.futurecdn.net, vanilla.futurecdn.net.

  • ✓

    Imagesmedium

    No <img> tags.

  • !

    Cachinglow

    Cache-Control: no-store,private

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

  • ✓

    HTTP/3low

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

Security 92%

Visitor safety signals that browsers and Google check.

  • ✓

    HTTPScritical

    Secure HTTPS with no mixed content.

  • ✓

    HTTP → HTTPS redirecthigh

    http:// redirects to https://.

  • ✓

    HSTSmedium

    HSTS: max-age=31536000; includeSubDomains

  • ✗

    Security headerslow

    Present: CSP, clickjacking protection.

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

  • ✓

    Server fingerprintlow

    No X-Powered-By header (server: cloudflare).

Mobile & accessibility 80%

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

  • ✓

    Mobile viewportcritical

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

  • ✓

    Image alt textmedium

    No images.

  • ✗

    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.