I'm Mansoor Bhanpurawala. I've done SEO since 2012. Technical SEO decides whether Google and AI crawlers can find, render, index and trust your pages. I audit the site, give your developers tickets they can build, then check every release.
Clicks to the gold-rates page of an Indian fintech platform in about 3 months. A footer hidden from crawlers and 302 redirects were the first fixes.
Monthly visits for a news site after a hack. Revenue went from Rs 5,000 to Rs 12,00,000 a month (client figures). 1.9 years.
Inquiries for an Indian B2B manufacturer, with schema, product page rebuilds and llms.txt in the work. Six months.
Monthly clicks for a US site that fell from about 300 to about 145, then climbed about 2x in three months.
Clicks I cost a client in one month by removing catalog pages without a traffic check. I now run a pre-mortem before any removal.
Clients since 2012, across fintech, SaaS, healthcare, home services, jewellery, education and B2B.
I started in SEO in 2012 and went fully independent in 2020. I hold the Google Analytics (GA4) certification and the Microsoft Advertising Certified Professional credential. Read the full story on my About page.
Every area below is done by me, from the crawl to the post-release check. I quote after I see your site.
Whether Google can reach every page that should earn traffic, and ignore the ones that should not.
How authority and crawlers move through the site.
Field data first, lab tests second.
What Googlebot actually sees, not what the browser shows you.
Where most self-inflicted traffic losses start.
Telling machines what a page is.
Right page, right market, right device.
Making sure AI search can read you, and deciding who may.
The order never changes. Skipping steps is how fixes break things.
I get Search Console, GA4, CMS or staging access and a developer contact. I ask what changed on the site in the last 12 months.
Full crawl, Search Console export, sitemap and robots.txt, PageSpeed and CrUX data, log files if you have them.
I group issues by template, not by URL. Fifty thousand product pages with one bug is one problem.
Each fix gets a severity: blocks indexing, loses links, slows revenue pages, or hygiene. Revenue pages go first.
One ticket per fix with the URL pattern, what is wrong, the exact change, how to test and the expected result.
I re-crawl staging or the live site after each release and use URL Inspection on samples.
Monthly report from Search Console and GA4: indexed pages, errors, vitals, clicks on fixed templates, what I do next.
This is the working list. Your site will fail some of these. Most sites fail more than ten. I rank the failures so you fix the costly ones first.
| Level | What it means | Example | When |
|---|---|---|---|
| 1. Blocks indexing | Google cannot or will not keep the page | Noindex on a product template, robots.txt block, soft 404s | First release |
| 2. Loses equity | Links and signals leak away | 302s on permanent moves, redirect chains, broken internal links | First or second release |
| 3. Slows revenue pages | Users and Google wait too long | LCP over 2.5 s on category pages, layout shifts on product pages | Within the first month |
| 4. Hygiene | Helps clarity, little immediate effect | Schema warnings, minor duplicate tags | Backlog |
Core Web Vitals thresholds I work to: LCP 2.5 s, INP 200 ms and CLS 0.1, measured at the 75th percentile of real visits. Google uses these as a page experience signal. Content relevance still outweighs them, so I fix vitals after indexing and equity problems.
Deleting "dead" products or posts often removes pages that still carry links and rankings. I cost one client 23% of clicks this way. Check clicks, links and rankings first, then redirect.
A temporary redirect on a permanent move leaves link signals in limbo. I found this on the fintech platform and fixed it in the first weeks.
The same fintech site had a footer that crawlers could not see. Links to key sections were invisible, so those sections starved.
A perfect Lighthouse score on a fast laptop means little. Core Web Vitals use real-user field data from the Chrome UX Report.
Theme, SEO plugin and a schema plugin each print Product or Organization markup. Conflicts confuse validators and waste effort.
Sitemaps full of redirected, noindexed or parameter URLs teach Google to ignore the file.
A firewall rule or CDN bot setting can shut out Googlebot and AI crawlers at once. Nobody notices until visibility drops.
Ten changes in one release hide which one helped or hurt. I stage releases so each result can be traced.
Crawlers find the problems. Search Console proves whether Google agrees.
These are client properties I worked on personally. Figures come from Google Search Console or the client. Clients agreed to show the data and asked me to keep their names out.
The B2B manufacturer lost 23% of clicks in one month after a catalog cleanup I did not test first. It happened again three months later. I report it because a case study with only upward lines is marketing, not proof.
Each chart draws the confirmed start and end values from Search Console as bars. They are not daily data and show no curve in between. Exact monthly values come from the CSV exports. Search Console measures clicks and impressions, not revenue. Each property had several kinds of work running at once, so no chart isolates one service. Client names are withheld at their request. Screenshots available on a call.
Each started with a crawl and a Search Console export, not a guess.
Found: a footer hidden from crawlers and 302 redirects where 301s belonged.
Did: fixed both first, then a news section, hub-and-spoke blog, gold and silver rate pages, programmatic stock pages.
Result: Gold-rates page reached 53.2K clicks in about 3 months and silver-rates 47.2K in about 2.
Found: a hacked site whose traffic had collapsed to about 6K visits a month.
Did: a recovery plan, run over 1.9 years.
Result: 6K to 300K monthly visits in 1.9 years. Revenue from Rs 5,000 to Rs 12,00,000 a month (client figures).
Found: 82% of clicks came from India. The business sells only abroad.
Did: rebuilt product pages, MOQ-led content, schema, llms.txt.
Result: 16 to 22 inquiries in six months, about half from GCC and tier-1 buyers.
Nobody can promise a date. These ranges come from my own projects.
Redirect fixes, sitemap clean-up and unblocked pages can show in Search Console within weeks.
Field data updates on a rolling 28-day window, so vitals gains show a month after release.
Re-crawling and re-indexing a big site takes months, not days.
Recovering a 50% traffic drop on the fintech platform took 16 months.
Your timeline depends on site size, crawl budget, developer speed and the cause of the problem.
Valid pages in Search Console against pages that should be indexed.
4xx, 5xx and redirect errors, trending to zero.
Share of URLs passing LCP, INP and CLS in field data.
Clicks and impressions for the page types I changed.
Requests, response time and host status in Search Console.
If a KPI does not move, I say so and change the plan. I will not hide behind "rankings improved."
I do not publish a price list, because the same budget buys different work depending on these factors. Message me on WhatsApp or call +91 90331 72192. I quote after I see your site.
A 40-page service site and a 200,000-URL store are different jobs.
Shopify limits some fixes. Custom builds need developer time.
JavaScript-heavy sites need extra testing.
A live traffic drop or a planned migration raises scope.
A single audit costs less than monthly release checks.
| Solo consultant (me) | SEO agency | Task-based freelancer | |
|---|---|---|---|
| Who does the work | The person you talk to. I do the crawling, ticket writing and release checks myself. | A team, with an account manager as your contact. | One person, often alongside a job or other clients. |
| Accountability | One person owns the strategy and the result. | Shared across a team and an account manager. | Owns the task, often not the outcome. |
| Speed of decisions | Same day. No approval chain. | Passes through account manager, strategist and executor. | Fast, but limited to the brief. |
| Reporting | Monthly from Search Console and GA4, written by me. | Dashboard plus a call with the account manager. | Varies from none to a spreadsheet. |
| What you pay for | Expert time. | Expert time plus management and overhead. | Task time. Quality varies the most. |
| Developer handover | Tickets written by the person who found the issue. | Often a long PDF handed to your team. | Usually a list of issues without test steps. |
A technical audit only pays when someone checks the fix. The person who finds the bug should be the person who checks the release.
I work with clients across India and abroad over video calls, WhatsApp and email.
Phone and WhatsApp: +91 90331 72192. Email: me@digitalmansoor.com.
Some important pages on our website were not appearing as expected in Google. Mansoor helped us investigate technical SEO issues and prioritize fixes. The process was methodical, and we could track the work completed.
The technical SEO audit helped us understand issues with our website structure, indexing, and internal links. Instead of giving us an overwhelming list, the recommendations helped us focus on the most important fixes first.
We wanted to improve the technical health of our website. Mansoor reviewed the key areas affecting crawling, page experience, and SEO. The findings gave our development team clearer steps to work on.
We were planning a website migration and wanted to avoid unnecessary SEO problems. Mansoor helped us review redirects, URLs, and important pages before the move. Having a clear checklist made the process easier to manage.
The SEO support during our website migration was useful. We received guidance on technical checks, indexing, and monitoring organic traffic after the launch. It helped our team approach the migration in a more organized way.
The schema markup work helped us address structured data issues on our website. We received guidance on implementation and validation, which made it easier for our development team to check the changes.
A technical SEO consultant finds and fixes the issues that stop search engines from crawling, rendering and indexing your pages: broken redirects, blocked resources, slow templates, duplicate URLs and missing structured data. I rank issues by impact, write developer tickets and check the release.
A full SEO audit covers content, links, local signals and technical health. A technical audit goes deeper on crawling, indexing, rendering, speed and structured data. If pages are not indexing or traffic fell after a release, start with the technical audit.
Small sites take about a week from access to written audit. Large stores and publishers take longer because the crawl and analysis take longer. I give a date after I see the site.
Both. On WordPress I can make many changes myself. On other stacks I write exact tickets for your developers and re-test after each release.
Core Web Vitals measure loading (LCP), responsiveness (INP) and layout stability (CLS) using real-user data. Google uses them as part of page experience. They matter, but content relevance and links still weigh more. Fix indexing and redirect problems first.
Sometimes. If the drop came from a technical cause such as a bad migration, blocked pages or lost redirects, fixing it can restore traffic. If it came from a core update or weak content, technical fixes alone will not. The fintech platform I worked on recovered after I fixed the crawl and redirect problems and rebuilt the content structure, but it took more than technical fixes.
If pages are not indexed, yes. Content on pages Google cannot reach earns nothing. If the site is healthy, content can run alongside.
No major AI search engine has confirmed that it uses llms.txt for ranking or citation. I add it as low-cost hygiene on request, not as a lever.
Yes. Valid, accurate structured data helps search engines understand pages and can make them eligible for rich results. Google has limited FAQ rich results to a narrow set of sites since 2023, so I add FAQ markup for clarity, not for extra snippets.
Yes. Platform limits change what is fixable. See my Shopify SEO and WooCommerce SEO pages.
Search Console and GA4 access, CMS or staging access, a developer contact and a list of site changes from the last year.
No. Nobody controls Google. I promise a ranked plan, release checks and honest monthly reports.
WhatsApp +91 90331 72192 · me@digitalmansoor.com