SEO report

SEO report for krakow.pl

https://krakow.pl/ · checked Sun, 01 Nov 2026 15:08 GMT

✓ 22 Passed! 7 Warnings✗ 17 FailedAI readiness 50%

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. XML sitemaphigh

    No XML sitemap found at /sitemap.xml or in robots.txt.

    Fix: Create an XML sitemap listing every page and submit it in Google Search Console.

    See the details

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

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

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

  6. Server response (TTFB)high

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

    See the details

  7. HTTP → HTTPS redirecthigh

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

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

    See the details

  8. Title tagcritical

    “Oficjalny serwis miejski - Oficjalny serwis miejski - Magiczny Kraków”

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

    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 krakow.pl…

Indexing & crawling 67%

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

    No XML sitemap found at /sitemap.xml or in robots.txt.

    Fix: Create an XML sitemap listing every page and submit it in Google Search Console.

  • ✗

    Canonical URLhigh

    No canonical tag.

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

  • ✓

    Redirectshigh

    Loads directly with no redirects.

  • ✗

    www / non-wwwmedium

    Both www.krakow.pl and krakow.pl load without redirecting – Google may see duplicate sites.

    Fix: Pick one version (with or without www) and 301-redirect the other to it.

Search snippet & sharing 54%

How the page looks in Google results and when shared.

  • !

    Title tagcritical

    “Oficjalny serwis miejski - Oficjalny serwis miejski - Magiczny Kraków”

    About 603px of Google's ~580px desktop width – it will probably be cut off.

    Repeated words: oficjalny, serwis, miejski.

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

  • ✓

    Meta descriptionhigh

    128 characters, ~833px 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 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.

  • ✗

    Faviconlow

    No favicon linked.

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

  • ✓

    Languagelow

    lang="pl"

Content quality 46%

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

  • ✓

    Word countmedium

    592 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

    Reading-ease scores only work for English; this page is lang="pl".

  • !

    Topic focushigh

    3 of 5 title keywords appear in the main content (missing: oficjalny, serwis).

    Fix: Use your main title phrases naturally in the opening paragraph and headings.

  • ✗

    H1 headingcritical

    No H1 heading.

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

  • ✓

    Heading structuremedium

    4 headings for 592 words.

    Levels are in order.

  • !

    Text-to-code ratiolow

    5% of the HTML is visible text.

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

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

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

  • ✗

    Server response (TTFB)high

    1816 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

    109 kB of HTML.

  • ✓

    Compressionmedium

    Compressed with gzip.

  • ✓

    Render-blocking resourceshigh

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

  • !

    Scripts & third partiesmedium

    21 script tag(s); files loaded from 0 other domain(s).

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

  • ✗

    Imagesmedium

    46 image(s).

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

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

    24 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: max-age=0, must-revalidate, private

    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, shrink-to-fit=no

  • ✓

    Image alt textmedium

    All 46 images have alt text.

  • ✓

    Form labelsmedium

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