Indexation drops
A set of pages loses index coverage over days or weeks and Search Console gives no clean cause.
One-problem diagnosis
SEO troubleshooting for one problem, not your whole site
Submit one SEO problem through the contact form and I look at it free. If I accept it, you pay $400 for one written diagnosis: what is wrong, why it matters, and what fixing it involves, with evidence behind every claim. If I decline it, you pay nothing and I tell you why. I'm Nipun Arora, a technical SEO and AI search visibility consultant working since 2014, and this is the fastest way to get a straight answer on the one thing that's actually wrong.
Price: $400, fixedConsulting since 2014Serves: United States and Dubai, UAE
What qualifies
Six kinds of problems that fit a single diagnosis
A problem qualifies when it is specific and nameable: something you can point at, not a general sense that the site "isn't doing as well as it should."
Deindexed pages
One page that used to rank stops appearing at all, and a manual reindex request keeps failing.
Rankings lost after a change
A migration, a redesign, or a CMS switch ships, and rankings fall in the weeks after.
Crawl anomalies
Search Console's crawl stats show a spike, a drop, or a pattern that doesn't match anything that changed on the site.
Rendering or hydration problems
The page looks complete in a browser and arrives broken, thin, or empty for a crawler rendering the JavaScript.
AI-assistant citation problems
ChatGPT, Perplexity, Gemini, Claude, or Google AI Mode names a competitor instead of you, describes your business wrongly, or never cites you at all.
Most SEO troubleshooting stops at Google. This one folds in the AI-search lane too, because a wrong or missing citation inside an assistant's answer is invisible on a Search Console dashboard and needs the same entity and schema reading the rest of this practice runs on. If Dubai is the specific market you're hiring for, start at SEO consultant in Dubai instead.
The builder edge
I read the code, not just the crawl
A crawl report tells you a page returned a 200. It does not tell you whether the JavaScript that page depends on actually ran.
A broken hydration boundary or a client-side redirect looks identical to a healthy page in a status-code report and completely different in a rendered DOM, and the rendered version is the one a buyer, and an AI assistant, actually sees. When the crawl data does not explain the symptom, I read the framework code behind it: the Astro islands, the redirect logic, the script that swaps content in after the page loads.
The same reading applies to the AI-search lane. Whether a page's JSON-LD actually resolves into a clean entity graph, or only looks like one to a human skimming the markup, decides whether an assistant can cite it correctly. A schema block that validates in a browser tab and fails to link up in practice is the same class of problem as a page that loads for a visitor and not for a crawler: code that looks right and isn't.
cool-astro-forms and this site's own build are the proof that reading holds up: MIT-licensed, versioned, published on npm, not a claim asking to be taken on faith.
House law
What this does not include
These limits are named up front because a diagnosis that quietly grows into more work is the exact failure mode a fixed-price offer exists to rule out.
No implementation. The diagnosis names the fix; making the fix is separate work, quoted separately if you want me to do it, or handed to whoever already maintains your site.
No calls. The answer arrives in writing, the same way every finding in a technical SEO audit does, so you end up with a document to act on instead of a call to remember.
No outcome guarantee. The diagnosis is accurate and evidenced. Whether a specific ranking or citation returns once the fix ships depends on more than one document, the same limit named on every service page here.
How it works
Three steps from submission to answer
Acceptance comes before payment, and payment comes before the answer, in that order, every time.
You submit the problem, free. One specific problem, through the contact form: what you are seeing, when it started, and what changed around that time if you know it. Looking at it costs nothing and commits neither of us to anything yet.
I accept or decline it, within two business days. A scoped, specific problem gets accepted, and you pay the fixed fee named above before I start. A problem that turns out to be the whole site, or something outside what a single diagnosis can answer, gets declined, and I tell you why. Either way, you pay nothing until I've accepted.
You receive one written diagnosis, within five business days of payment. What is wrong, why it matters, and what fixing it involves, with the evidence behind each claim: a screenshot, a log line, a rendered-DOM diff, whatever the problem actually produced. Nothing else ships inside this offer.
Submit one problem, and I'll tell you if it fits.
Submit a problemQuestions
Questions before you submit a problem
Why a fixed fee instead of a quote?
The same fixed-scope discipline every engagement here runs on: a number agreed before work starts, not a back-and-forth over one problem. Submitting the problem is free either way, so you see the fee before you commit to it.
What happens if you decline the problem?
You pay nothing, and you get a plain reason: the problem sits outside what one diagnosis can answer, it needs the full five-check technical SEO audit instead, or it isn't actually an SEO problem. Declining is a real answer, not a stall.
How is this different from the technical SEO audit?
Scope. The technical SEO audit runs five checks across a whole site and hands back one prioritized fix list. This runs one check against one named problem and hands back one written diagnosis. A site with several unrelated problems needs the audit; a site with one problem it can name needs this.
Does this cover AI-search problems, or only Google?
Both. A wrong or missing citation inside ChatGPT, Perplexity, Gemini, Claude, or Google AI Mode qualifies the same way a crawl or index problem does. The ongoing version of that work, measured across all five engines, lives on the AI search visibility page.
How fast do I get an answer?
A decision on whether the problem is accepted lands within two business days of submitting it. Once accepted and paid, the written diagnosis lands within five business days.
What counts as 'one problem'?
A single, specific, nameable symptom: an indexation drop, a deindexed page, a rankings loss tied to one change, a crawl anomaly, a rendering or hydration problem, or an AI-assistant citation problem. A request to audit the whole site under a different name gets declined and pointed at the audit page instead.
Do you need access to my site to answer this?
Not to submit it. A URL, a description of what you're seeing, and when it started are enough to decide whether the problem is accepted. If the diagnosis itself needs a closer look, a staging login or a server log, I ask for exactly what's needed once I've accepted the problem, not before.
Describe the one thing that's wrong. Choose "SEO troubleshooting" from the form's dropdown, and I'll tell you within two business days whether it fits.
Submit a problem