SEO report

SEO report for tergeo.com.pl

https://tergeo.com.pl/ · checked Sun, 01 Nov 2026 21:47 GMT

✓ 21 Passed! 10 Warnings✗ 14 FailedAI readiness 38%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. 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

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

  3. Render-blocking resourceshigh

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

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

    See the details

  4. HTTP → HTTPS redirecthigh

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

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

    See the details

  5. Title tagcritical

    “Tergeo | Geodezja”

    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

  6. H1 headingcritical

    “TERGEO”

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

    On WordPress: Most themes show the page title as the H1. In the editor, make sure no other block uses Heading 1 – use Heading 2 for sections.

    See the details

  7. HTTPScritical

    1 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. Mobile viewportcritical

    viewport: width=device-width, minimum-scale=1, maximum-scale=1 – blocks pinch-zoom

    Fix: Use <meta name="viewport" content="width=device-width, initial-scale=1"> and allow zoom.

    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 tergeo.com.pl…

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://tergeo.com.pl/sitemap.xml listing 81 sitemaps.

    Declared in robots.txt.

    Most recent lastmod: 2026-11-01T21:47:43+00:00.

  • ✓

    Canonical URLhigh

    Canonical: https://tergeo.com.pl/

    Points to this page (self-referencing).

  • ✓

    Redirectshigh

    Loads directly with no redirects.

  • ✓

    www / non-wwwmedium

    www.tergeo.com.pl redirects to tergeo.com.pl.

Search snippet & sharing 50%

How the page looks in Google results and when shared.

  • !

    Title tagcritical

    “Tergeo | Geodezja”

    About 165px 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.

    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

    15 characters, ~111px of ~990px.

    Short – sell the click with a benefit and a call to action.

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

    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

    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

    13,704 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 30 (fairly difficult), about 10 words per sentence.

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

  • ✓

    Topic focushigh

    1 of 1 title keywords appear in the main content.

  • !

    H1 headingcritical

    “TERGEO”

    The H1 shares no keywords with the title.

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

    On WordPress: Most themes show the page title as the H1. In the editor, make sure no other block uses Heading 1 – use Heading 2 for sections.

  • !

    Heading structuremedium

    4 headings for 13704 words.

    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

    60% of the HTML is visible text.

AI search readiness 38%

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

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

Machine-readable facts for rich results and AI.

Performance 37%

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

  • !

    Server response (TTFB)high

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

    Fix: Use page caching or a CDN (e.g. Cloudflare) so HTML is served from the edge.

  • !

    HTML sizemedium

    164 kB of HTML.

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

  • ✓

    Compressionmedium

    Compressed with gzip.

  • ✗

    Render-blocking resourceshigh

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

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

  • ✗

    Scripts & third partiesmedium

    31 script tag(s); files loaded from 1 other domain(s): fonts.googleapis.com.

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

  • !

    Imagesmedium

    1 image(s).

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

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

  • 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 29%

Visitor safety signals that browsers and Google check.

  • !

    HTTPScritical

    1 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:// does not redirect to https://.

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

  • ✗

    HSTSmedium

    No Strict-Transport-Security header.

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

  • ✗

    Security headerslow

    Present: none.

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

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

  • !

    Mobile viewportcritical

    viewport: width=device-width, minimum-scale=1, maximum-scale=1 – blocks pinch-zoom

    Fix: Use <meta name="viewport" content="width=device-width, initial-scale=1"> and allow zoom.

  • ✓

    Image alt textmedium

    All 1 images have alt text.

  • ✗

    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.