SEO report

SEO report for open-techstack.com

https://open-techstack.com/ · checked Thu, 05 Nov 2026 00:08 GMT

✓ 32 Passed! 8 Warnings✗ 6 FailedAI readiness 66%

Fix these first

  1. HTTP → HTTPS redirecthigh

    http:// does not redirect to https://.

    Fix: 301-redirect all http:// requests to https://.

    See the details

  2. Title tagcritical

    “Open-TechStack”

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

    See the details

  3. H1 headingcritical

    “Practical AI analysis for people who actually build .”

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

    See the details

  4. Freshness signalsmedium

    No published/updated date found.

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

    See the details

  5. HSTSmedium

    No Strict-Transport-Security header.

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

    See the details

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

  7. Entity clarityhigh

    Identified as: Person.

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

    See the details

  8. Readabilitymedium

    Flesch reading ease 48 (fairly difficult), about 12 words per sentence.

    Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.

    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 open-techstack.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://open-techstack.com/sitemap-index.xml listing 1 sitemap.

    Declared in robots.txt.

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

  • ✓

    Canonical URLhigh

    Canonical: https://open-techstack.com/

    Points to this page (self-referencing).

  • ✓

    Redirectshigh

    Loads directly with no redirects.

  • ✓

    www / non-wwwmedium

    www.open-techstack.com isn't in use (HTTP 530).

Search snippet & sharing 79%

How the page looks in Google results and when shared.

  • !

    Title tagcritical

    “Open-TechStack”

    About 150px of Google's ~580px desktop width – short; use the space.

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

  • ✓

    Meta descriptionhigh

    108 characters, ~669px of ~990px.

    Good length.

    Google sometimes rewrites descriptions to match the search; a good one is still used most often.

  • ✓

    Open Graph & social cardsmedium

    Open Graph title and image set.

    Twitter/X card: summary_large_image.

  • ✓

    Faviconlow

    Favicon linked (Google shows it next to results).

  • ✓

    Languagelow

    lang="en"

Content quality 70%

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

  • ✓

    Word countmedium

    2,097 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 48 (fairly difficult), about 12 words per sentence.

    Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.

  • ✓

    Topic focushigh

    2 of 2 title keywords appear in the main content.

  • !

    H1 headingcritical

    “Practical AI analysis for people who actually build .”

    The H1 shares no keywords with the title.

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

  • !

    Heading structuremedium

    61 headings for 2097 words – a lot for the amount of text.

    1 skipped level(s), e.g. H2 → H4.

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

  • ✓

    Text-to-code ratiolow

    15% of the HTML is visible text.

AI search readiness 66%

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

    2 heading(s) phrased as questions, e.g. “How to Set Up Multi-Provider AI Routing in Laravel”.

    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: Person.

    No sameAs links to official profiles (Google Business Profile, LinkedIn, Facebook, Companies House…).

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

  • ✗

    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

    Links found to all three: about, contact and privacy.

Structured data 100%

Machine-readable facts for rich results and AI.

  • ✓

    JSON-LD present & validhigh

    1 JSON-LD block(s): WebSite, Person.

    All blocks parse correctly.

  • ✓

    Required propertiesmedium

    Key types include Google's required properties.

  • i

    Breadcrumbslow

    Home page – breadcrumbs not needed.

Performance 88%

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

  • ✓

    Server response (TTFB)high

    53 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

    94 kB of HTML.

  • i

    Compressionmedium

    Couldn't be measured from our server (our fetch decodes compressed pages before we see them). Check in your browser's developer tools that HTML is sent with br or gzip.

  • ✓

    Render-blocking resourceshigh

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

  • ✓

    Scripts & third partiesmedium

    10 script tag(s); files loaded from 2 other domain(s): googletagmanager.com, pagead2.googlesyndication.com.

  • !

    Imagesmedium

    50 image(s).

    All images reserve their space.

    The first image is lazy-loaded – if it's the main (LCP) image, that delays it. Don't lazy-load images visible on arrival.

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

  • !

    Cachinglow

    Cache-Control: public, max-age=0, must-revalidate

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

  • i

    HTTP/3low

    Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.

Security 50%

Visitor safety signals that browsers and Google check.

Mobile & accessibility 83%

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

  • ✓

    Mobile viewportcritical

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

  • ✓

    Image alt textmedium

    All 50 images have alt text.

  • ✓

    Form labelsmedium

    All 1 form fields are labelled.

  • ✗

    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.