vatanny.com: homepage SEO audit

Two page elements have a fixed width, which can cause them to spill past the edges of smaller phone screens and lowers the site's mobile score. The site loads quickly and is fully secure, and its page titles and link descriptions are set up well. The most useful next step is to replace the fixed widths on those two elements with flexible widths so the content adjusts to each screen size.

1. 01
   ImportantMobile

   2 elements have a fixed width

   Some parts of this page use a fixed pixel width wider than 500px. These can spill off the side of a phone screen and force annoying sideways scrolling.

   How to fix: Use flexible widths (%, max-width) instead of fixed pixel widths so content adapts to small screens.

2. 02
   ImportantContent & SEO Readiness

   AI assistants like ChatGPT are blocked

   The site's robots.txt blocks ChatGPT (GPTBot), Claude (ClaudeBot), Google AI (Google-Extended), Common Crawl (CCBot). These are the crawlers ChatGPT, Perplexity and Google's AI answers use to learn about — and recommend — a business. While they're blocked, this site can't show up when a customer asks an AI assistant for a business like it.

   How to fix: In robots.txt, remove the "Disallow: /" that applies to these bots — under their own User-agent lines, or under "User-agent: *" if they have none — so AI assistants are allowed to read the public pages.

3. 03
   MinorHeadings

   Headings skip levels

   Headings work like a table of contents (H1 → H2 → H3). This page jumps a level somewhere, which makes the structure harder for Google and screen readers to follow.

   How to fix: Use headings in order — don't jump from H2 straight to H4. Pick heading levels for structure, not for font size (use CSS for styling).

4. 04
   MinorContent & SEO Readiness

   Few links to other pages on this site

   Internal links help visitors explore your site and help Google discover all your pages. Link from your homepage to your key services and content.

   How to fix: Add navigation links from your homepage to your main pages (what you offer, about, contact).

5. 05
   MinorContent & SEO Readiness

   No llms.txt file found

   llms.txt is a new, simple file that tells AI assistants like ChatGPT what your business does and which pages matter most — making it easier for them to describe and recommend you accurately. It's optional today, but an easy edge while most sites don't have one.

   How to fix: Add a plain-text /llms.txt at the root of your site summarising your business and linking your key pages. We can generate one for you.

6. 06
   MinorContent & SEO Readiness

   No published or updated date

   This page shows no published or "last updated" date. Both Google and AI assistants favour content that is clearly current, and a visible date is the simplest freshness signal — undated pages look stale even when they aren't.

   How to fix: Show a published or "Last updated" date on the page, and add datePublished / dateModified to your structured data.

7. 07
   MinorContent & SEO Readiness

   Question headings without a direct answer

   Your page poses questions in its headings but doesn't answer them concisely right below. AI assistants and Google's AI Overviews quote the short passage that directly resolves a question — a 1–3 sentence answer immediately under the heading — so a question with no tight answer beneath it rarely gets pulled.

   How to fix: Under each question heading, put a direct 1–3 sentence answer first, then expand. Lead with the answer, not the build-up.

• !AI assistants like ChatGPT are blocked
• !No llms.txt file found
• ✓This page uses structured data
• !Question headings without a direct answer
• ✓This page uses question-style headings
• ✓This page shows who wrote it
• !No published or updated date
• ✓This page includes data points

• ✓The page title is a good length
• ✓The page has a single title
• ✓The meta description is a good length
• ✓Social sharing preview is set up
• ✓This page tells Google which version is the main one
• ✓This page has exactly one main heading
• ✓The main heading is a good length
• ✓This page responded quickly (0.2s)
• ✓This page's code is a healthy size (19KB)
• ✓This page has a reasonable number of images
• ✓This page loads without a redirect chain
• ✓Nothing is blocking this page from displaying
• ✓This page is set up to fit mobile screens
• ✓This site uses a secure (HTTPS) connection
• ✓All content loads securely
• ✓This page has plenty of content (886 words)
• ✓Most images have descriptions
• ✓This site has a favicon
• ✓This site has a robots.txt file
• ✓Search engines are allowed to show this page
• ✓Search engines are allowed to crawl this site
• ✓This site has a sitemap