What our audit actually checks — before / after examples

Pillar 1 of 5

SEO-friendly

The myth: "If my site is on Google somewhere, I'm fine."

The reality: Being indexed isn't the same as being findable. SEO is about giving Google the right signals — titles, descriptions, headings, structured data — so it knows when to show your page and what to display in the result.

Example: how your homepage looks in Google search

❌ Generic — easy to skip

example-store.com

Home

Welcome to our website. We sell products. Click here to know more.

<title>Home</title>
<meta name="description"
      content="Welcome to our
              website.">
<!-- no structured data -->

✓ Specific — gets the click

sharma-electronics.in

Sharma Electronics — Sitabuldi, Nagpur · Mixers, fans, ACs

Family-run electronics store in Sitabuldi since 1985. Same-day delivery in Nagpur. EMI on orders above ₹5,000.

<title>Sharma Electronics — Sitabuldi, Nagpur · Mixers, fans, ACs</title>
<meta name="description"
      content="Family-run
      electronics store in Sitabuldi since
      1985. Same-day delivery in Nagpur...">

How the audit tests this: we scan every crawled page for a unique, descriptive title (10–60 chars), a meta description (50–160 chars), a single H1 with the main page topic, and at least one structured-data block. Missing or duplicate titles get flagged as warnings.

Pillar 2 of 5

Mobile-ready

The myth: "I checked on my phone, it opens fine."

The reality: "Opens" isn't the same as "usable." Mobile-ready means text is readable without zooming, buttons are far enough apart that thumbs don't mis-tap, and the page loads fast on a slow 4G connection — not the office WiFi the developer tested on.

Example: tap targets too close vs far enough apart

❌ Buttons too small, too close

<button style="padding:4px
                6px; font-size:11px">
  Buy
</button>
/* Thumb hits Wishlist by mistake */

✓ 44px+ targets, generous spacing

<button style="padding:12px
                14px; font-size:14px;
                margin-bottom:8px">
  Buy now
</button>
/* Easy to hit, easy to read */

How the audit tests this: we render the page at a 360×640 viewport (smallest common Indian phone), measure tap-target sizes (target: ≥ 44×44 px), check viewport meta tag, measure load time on a throttled 4G profile, and flag any text smaller than 12px.

Pillar 3 of 5

AI-ready

The myth: "AI? My customers Google me, they don't use ChatGPT."

The reality: Google's AI Overview already answers 30%+ of searches before showing blue links. ChatGPT, Gemini, and Perplexity all extract facts from websites. If your site doesn't tell AI tools who you are in machine-readable form, they'll guess — or skip you entirely.

Example: how AI sees your business

❌ No structured data

Ask: "Best mixer-grinder shop in Sitabuldi?"

AI: "I don't have specific information about shops in Sitabuldi. You may want to search Google Maps directly."

<body>
  <h1>Sharma Electronics</h1>
  <p>We sell mixers and fans.</p>
</body>
<!-- no JSON-LD, no llms.txt -->

✓ With JSON-LD + llms.txt

Ask: "Best mixer-grinder shop in Sitabuldi?"

AI: "Sharma Electronics in Sitabuldi, Nagpur is a family-run electronics store since 1985 specialising in mixers, fans and ACs. They offer same-day delivery and EMI."

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Sharma Electronics",
  "address": { ... },
  "foundingDate": "1985"
}
</script>

How the audit tests this: we fetch /llms.txt, parse /robots.txt for rules covering GPTBot, ClaudeBot, Google-Extended, PerplexityBot and others, count JSON-LD blocks and check for Organization/LocalBusiness types, verify author + publication metadata, and confirm a valid sitemap.

Pillar 4 of 5

Accessible

The myth: "Accessibility is for blind people. I don't have any blind customers."

The reality: Accessibility helps everyone: a low-contrast button is invisible to elderly customers and to anyone reading outside in bright sunlight. Alt text on product images becomes searchable on Google. A keyboard-navigable form helps a customer with a broken touchscreen. WCAG accessibility correlates strongly with conversion rate.

Example: button contrast on a sunlit phone screen

❌ Low contrast — invisible outside

Add to cart

<button style="background:#f1f5f9;
                color:#cbd5e1">
  Add to cart
</button>
/* Contrast ratio: 1.6 (fails WCAG) */

✓ High contrast — readable anywhere

Add to cart

<button style="background:#1e3a5f;
                color:#ffffff">
  Add to cart
</button>
/* Contrast ratio: 11.5 (WCAG AAA) */

Example: product image without and with alt text

❌ No alt — screen reader says "image"

<img
  src="/images/mixer-bajaj-500w.jpg"
>
/* Google can't index this product. */
/* Screen reader skips it. */

✓ With alt — searchable + readable

<img
  src="/images/mixer-bajaj-500w.jpg"
  alt="Bajaj 500W mixer-grinder
       with 3 jars, black"
>
/* Indexable by Google Images. */
/* Read out by screen readers. */

How the audit tests this: we check colour-contrast ratios on text and buttons (WCAG AA threshold 4.5:1 for normal text, 3:1 for large text), count images missing alt text, look for unlabelled form fields, verify keyboard-only navigation works, and check for ARIA landmarks (header, nav, main, footer).

Pillar 5 of 5

Secure & Trusted

The myth: "I have HTTPS, so my site is secure."

The reality: HTTPS is the front door's lock. Security headers are the alarm system, the cameras, and the smoke detector. A visitor (or Google) can tell the difference within seconds — and 84% of shoppers say they leave a site that looks untrustworthy.

Example: what the browser address bar shows

❌ HTTPS only, expired cert

⚠ example-store.com

Your connection is not private.

/* Certificate expired 12 days ago.
   No HSTS header — first-time
   visitors loaded over HTTP and
   any login was sent in plain text. */

✓ HTTPS + HSTS + valid cert

🔒 sharma-electronics.in

Connection is secure.

/* Cert valid for 89 days, auto-renews.
   HSTS header forces HTTPS for all
   future visits (max-age=63072000).
   No mixed content. */
Strict-Transport-Security:
  max-age=63072000;
  includeSubDomains

Example: trust signals on the page itself

❌ Anonymous — feels like a scam

<footer>
  © 2025 example-store
  <!-- no address -->
  <!-- no phone -->
  <!-- no privacy policy -->
  <!-- no GST/registration -->
</footer>

✓ Real business signals

<footer>
  Sharma Electronics
  Shop 12, Sitabuldi Main Road, Nagpur 440012
  Phone: +91 555-0100 · GSTIN: 27AAACS1234A1Z5
  <a href="/privacy/">Privacy</a> ·
  <a href="/terms/">Terms</a>
</footer>

How the audit tests this: we verify SSL cert validity and expiry, check for HSTS/CSP/X-Frame-Options/X-Content-Type-Options/Referrer-Policy/Permissions-Policy headers, scan every HTTPS page for mixed-content (HTTP resources), look for a privacy policy and terms page, and check the footer for real business identification.