MotorPedia SEO Audit — themotorpedia.com (Oct 2026)

<aside> 🔍

Website: themotorpedia.com · Stack: Next.js, ImageKit CDN, Google Tag Manager

Audit date: October 5, 2026 · Audited by: Prashant Kumar Pandey, Digital Marketing Manager

Scope: technical SEO, indexing & sitemaps, on-page, programmatic pages, content, search visibility and competitors.

</aside>

📊 Executive Summary

<aside> 🔴

3 critical

issues

</aside>

<aside> 🟠

4 high

priority

</aside>

<aside> 🟡

6 medium

priority

</aside>

<aside> ✅

8 strengths

to keep

</aside>

MotorPedia has a strong SEO foundation — good titles, canonicals, broad sitemap coverage and 3,000+ programmatic pages targeting city, brand and service searches. But the pages appear to deliver their content through JavaScript, have no H1s or schema, and the city pages are thin. As a result, MotorPedia does not appear in the top 10 for its own core searches, which are dominated by CarWale, Spinny, insurers and finance brands. Fixing rendering, headings and schema is the single biggest unlock.

🗺️ Site Inventory (from XML sitemaps)

Section	URLs	URL pattern	Target search intent
Used-car listings (city / brand / model / body type)	1,006	/used-cars+bmw+5-series+in+delhi-ncr	"used BMW 5 Series in Delhi"
Used-car detail pages	500+	/used-car-details/hyundai-creta-sx-used-car-in-delhi-ncr-[UUID]	Specific car for sale
Challan check by city	1,000+	/challan-check+in+gurgaon+haryana	"challan check Gurgaon"
Vahan / RTO services by city	500+	/vahan-rto-services+in+pune	"RTO services Pune"
Blog	16 (≈ 9 posts + 7 hub pages)	/blog/category/buyers-roadmap	Guides, news, comparisons
Insurance, inspection, car loan, EMI & fuel calculators, fancy numbers, service history	Several sitemaps	Mixed	Service & tool searches

The sitemap index lists 17 sitemaps; robots.txt lists 16. In total the site submits 3,000+ URLs to Google.

🔴 Critical Issues

1. Page content isn't in the HTML Google first receives

Finding: Fetched HTML for the homepage, a city listing page, the challan page, the blog and a blog category returned only head tags (title, meta, canonical, GTM). No H1, headings, listings, copy or links were present in the response.
Why it matters: Google has to queue the page for JavaScript rendering before it sees any content, which slows and weakens indexing — especially across 3,000+ pages. Bing, social previews and AI search crawlers (ChatGPT, Perplexity) often don't render JS at all.
Fix: Use Next.js server-side rendering or static generation (getServerSideProps / getStaticProps or App Router server components) for all public pages. Verify in Search Console → URL Inspection → "View crawled page".

2. No H1 or heading structure

Finding: No H1 or H2 found on any page checked.
Fix: One H1 per page matching the main keyword (e.g. "Used Cars in Delhi", "Online Challan Check in Gurgaon"), with H2s for listings, FAQs and related links.

📊 Executive Summary

🗺️ Site Inventory (from XML sitemaps)

🔴 Critical Issues

1. Page content isn't in the HTML Google first receives

2. No H1 or heading structure

3. 3,000+ thin programmatic pages