SEO report

SEO report for www.wikivoyage.org

https://www.wikivoyage.org/ · checked Sun, 01 Nov 2026 17:15 GMT

✓ 25 Passed! 2 Warnings✗ 17 FailedAI readiness 38%

Fix these first

  1. Mobile viewportcritical

    viewport: initial-scale=1,user-scalable=yes

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

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

    See the details

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

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

  7. Internal linkinghigh

    0 internal and 53 external links.

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

    See the details

  8. Title tagcritical

    “Wikivoyage”

    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 wikivoyage.org…

Indexing & crawling 75%

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

    1 redirect before the page loaded.

    https://wikivoyage.org/ → https://www.wikivoyage.org/

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

  • ✓

    www / non-wwwmedium

    wikivoyage.org redirects to www.wikivoyage.org.

Search snippet & sharing 38%

How the page looks in Google results and when shared.

Content quality 70%

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

  • ✗

    Word countmedium

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

    Fix: Add genuinely useful content: key service pages usually need 400+ words to answer what customers ask.

  • i

    Readabilitymedium

    Not enough paragraph text to score readability.

  • i

    Topic focushigh

    No title keywords to compare.

  • ✓

    H1 headingcritical

    “Wikivoyage Free travel guide”

  • ✓

    Heading structuremedium

    4 headings for 105 words.

    Levels are in order.

  • ✗

    Text-to-code ratiolow

    2% of the HTML is visible text.

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

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

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

  • ✓

    Server response (TTFB)high

    284 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

    62 kB of HTML.

  • ✓

    Compressionmedium

    Compressed with gzip.

  • ✓

    Render-blocking resourceshigh

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

  • ✓

    Scripts & third partiesmedium

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

  • ✓

    Imagesmedium

    1 image(s).

    All images reserve their space.

    1 use WebP/AVIF or responsive srcset.

  • ✓

    Cachinglow

    Cache-Control: s-maxage=86400, must-revalidate, max-age=3600

  • 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 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=106384710; includeSubDomains; preload

  • ✗

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

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

  • ✗

    Mobile viewportcritical

    viewport: initial-scale=1,user-scalable=yes

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

  • !

    Image alt textmedium

    1 of 1 images have no alt attribute.

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

  • ✗

    Form labelsmedium

    1 of 2 form field(s) have no label.

    Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).

  • ✗

    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.