You will get a technical SEO audit showing why Google is not indexing your pages
Rising Talent
Project details
If your site has thousands of pages and only a fraction are in Google's index, this audit tells you exactly why.
I built a 250,000-page Next.js site, watched Google mass-deindex it, and measured my way out. That method is what you are buying here.
What I do:
• Pull your real index status page by page through the Search Console URL Inspection API, not a third-party estimate
• Measure how similar your pages actually are to each other, because near-duplicate content is the usual reason programmatic pages get dropped
• Check the boring killers: robots rules, canonicals, sitemap mismatches, JS-rendered content crawlers never see, hosting settings that block Googlebot
• Rank every finding by how many pages it affects
What you get: the numbers, the cause, and a fix list in priority order. If the honest answer is "cut pages, do not add them," I will say that.
Best fit for programmatic, directory, location-page or catalogue sites from 500 pages up. Small brochure sites usually do not need this.
I built a 250,000-page Next.js site, watched Google mass-deindex it, and measured my way out. That method is what you are buying here.
What I do:
• Pull your real index status page by page through the Search Console URL Inspection API, not a third-party estimate
• Measure how similar your pages actually are to each other, because near-duplicate content is the usual reason programmatic pages get dropped
• Check the boring killers: robots rules, canonicals, sitemap mismatches, JS-rendered content crawlers never see, hosting settings that block Googlebot
• Rank every finding by how many pages it affects
What you get: the numbers, the cause, and a fix list in priority order. If the honest answer is "cut pages, do not add them," I will say that.
Best fit for programmatic, directory, location-page or catalogue sites from 500 pages up. Small brochure sites usually do not need this.
Language
EnglishWhat's included $300
These options are included with the project scope.
$300
- Delivery Time 5 days
- Site SEO Audit
- Index Optimization
- XML Sitemap
- Robots.txt
Optional add-ons
You can add these on the next page.
Fast 2 Days Delivery
+$100Frequently asked questions
1 review
(1)
(0)
(0)
(0)
(0)
This project doesn't have any reviews.
RP
Raj P.
Aug 12, 2026
Senior Astro + Sanity + Vercel Engineer
Haider is exceptional. He doesn't just execute instructions — he thinks like a technical architect, SEO strategist, and product designer at the same time.
What impressed me most was his ability to anticipate problems before they became problems. He didn't blindly follow the scope; he identified UX issues, SEO risks, technical gaps, security concerns, and patient-experience problems, then explained the tradeoffs clearly before making recommendations.
He moved incredibly fast without sacrificing quality. What was originally scoped as a 5–7 week timeline was executed at an extraordinary pace, while still producing a robust production infrastructure, automated deployment pipeline, migration plan, rollback process, SEO foundation, AI-crawler accessibility, performance optimization, and a clean launch.
He is the rare developer who understands the business behind the code. He consistently asked, “What happens to the user?” and “What happens at scale?” rather than simply asking whether something technically works.
Communication was excellent, execution was excellent, and his attention to detail was exceptional. He also challenged my assumptions when he saw a better path — and importantly, he explained why.
I would absolutely work with Haider again. If you want someone who can take ownership, think several steps ahead, move fast, and build things properly, hire him.
10/10. Highly recommended
What impressed me most was his ability to anticipate problems before they became problems. He didn't blindly follow the scope; he identified UX issues, SEO risks, technical gaps, security concerns, and patient-experience problems, then explained the tradeoffs clearly before making recommendations.
He moved incredibly fast without sacrificing quality. What was originally scoped as a 5–7 week timeline was executed at an extraordinary pace, while still producing a robust production infrastructure, automated deployment pipeline, migration plan, rollback process, SEO foundation, AI-crawler accessibility, performance optimization, and a clean launch.
He is the rare developer who understands the business behind the code. He consistently asked, “What happens to the user?” and “What happens at scale?” rather than simply asking whether something technically works.
Communication was excellent, execution was excellent, and his attention to detail was exceptional. He also challenged my assumptions when he saw a better path — and importantly, he explained why.
I would absolutely work with Haider again. If you want someone who can take ownership, think several steps ahead, move fast, and build things properly, hire him.
10/10. Highly recommended
About Haider
Technical SEO + AI Search (GEO/AEO) | Next.js & Vercel Engineer
Karachi, Pakistan - 1:35 pm local time
I measure that answer instead of guessing at it.
Last year I built a 250,000-page Next.js site. Google indexed it, then mass-deindexed it. I measured 6-gram similarity between pages (59-64% overlap, only 22-26% unique text), confirmed it page-by-page through the URL Inspection API, then rebuilt the pages on real external data - NOAA climate normals, US Census housing, Wikidata entity links - for 4,800 cities. When that only moved uniqueness from 26% to 34%, I told the owner the truth and we cut the site to 38,728 pages, keeping the ones that had actually produced phone calls.
That is the same discipline AI search rewards. Models cite sources that are specific, structured and verifiable. Thin pages do not get cited any more than they get indexed.
WHAT I DO
- AI search visibility (GEO / AEO) - entity schema with Wikipedia/Wikidata sameAs, llms.txt, structured data and factual density that make you the citable source
- Indexing and deindexing diagnosis - "Crawled - currently not indexed", crawl budget, thin and duplicate content, canonical and sitemap mismatches
- CMS migration without losing rankings - WordPress to headless (Sanity, Astro, Next.js) on Vercel: scripted content ETL, 301 redirect maps, canonical preservation, then a launch verification battery that re-checks every URL on the live domain. Last one shipped in 3 days for a telehealth practice - the 5.0 review on this profile is that client
- Programmatic / pSEO builds in Next.js - data model, URL architecture, content engine, sitemaps, schema, ISR, the whole pipeline
- Technical SEO forensics - I've traced total traffic loss to Vercel Deployment Protection, Vercel Attack Challenge Mode blocking Googlebot, and a prerender script shipping a 0-character homepage to crawlers
- Full-stack build - Next.js, Astro, Sanity, React, TypeScript, Tailwind, Supabase, Shopify Hydrogen, Cloudflare Workers/Pages, Stripe, Twilio
HOW I WORK
I use APIs, not dashboards. Search Console Search Analytics, URL Inspection and Indexing APIs across 22 properties. Ahrefs API filtered on serp_domain_rating_top10_min - so I only target keywords where a weak site ALREADY ranks top 10, which is proof of entry instead of a difficulty guess. Every claim I make comes with the query that produced it.
I will also tell you when the answer is "don't build this." I've killed several of my own projects with keyword research, and I'd rather lose a week of billing than build you 40,000 pages Google will delete.
Currently running 36 production sites across Vercel and Cloudflare, roughly 3,150 commits in the last 12 months.
ALSO SHIPPED (all live - links on request)
- Two React Native (Expo) apps on Google Play: a real-time fare-bidding rides marketplace on Supabase, and an AI resume builder with an OpenRouter model registry behind it
- A headless Shopify storefront with an in-browser product designer (Fabric.js, print-ready PDF pipeline) that carries 100% of that store's orders
- A contractor material-calculator hub selling a Pro tier through Paddle: licence keys, HMAC-verified webhooks, Cloudflare Workers and KV
- An 8,675-record farmers-market directory on Next.js + Supabase, now at roughly 1,700 Google clicks a month
HOW I BUILD
I work in Claude Code daily and ship the tooling around it: a credential-free site diagnostic, a 21-check pre/post cutover battery that machine-checks MX and TXT survival, a CI step that fails the build on a stray noindex, a bot-parity byte-diff across GPTBot, ClaudeBot and PerplexityBot versus a browser, and an IndexNow submitter. If your team wants its CMS wired to Claude or ChatGPT through MCP, that is something I have already done.
If your site is losing pages, never got indexed, or is invisible in AI answers - send me the domain and I'll tell you what I see before you pay anything.
Steps for completing your project
After purchasing the project, send requirements so Haider can start the project.
Delivery time starts when Haider receives requirements from you.
Haider works on your project following the steps below.
Revisions may occur after the delivery date.
You send the domain and Search Console access
I run the index, crawl and page-similarity analysis