Company / About
I built SerpDad for the day someone asks why this page exists.
I'm Asif. For years I ran SEO for B2B SaaS companies, and every quarter the number had my name on it. SerpDad is the habit I kept on those jobs, turned into a product: decide from the live results, and keep the receipt.
Written by Khondokar MD Asiful Islam (Asif), co-founder. Last checked 21 Oct 2026.
Before SerpDad, I built SEO for B2B SaaS companies from the inside. I hired and trained the team. I paid the vendors. I built the process. At the end of every quarter, the number had my name on it.
That changes how you work. When you own the number, you cannot defend a page list that came from an export, a spreadsheet and someone's memory of the site. So you read the results Google already shows, you test, and you keep the evidence.
SerpDad does that for every keyword you give it, and it keeps the evidence for you. It is young and it is small. This page says so, with numbers.
The habit, shown. Every claim gets one of three labels.
When the Google Content Warehouse documentation leaked, most of the commentary was secondhand. I read every one of its 14,062 fields and published the whole reading free on Missing Intent, with each field searchable in the Signal Explorer. No email wall.
Everything I write there carries a label. Proven means documented, with a source you can open. Testing means a theory still being checked. Unknown means nobody outside Google can know it yet.
This site runs on the same rule. On the right are three claims about SerpDad itself, labelled the way I label a leak field. The third one matters most: we will never move it to Proven, because we cannot.
Source: the provider bill and the run record, 20 Oct 2026. Open the run
Not checked yet. serpdad.com is new, and a Search Console check-in is planned on the build log.
Rankings move for many reasons. When our numbers move, we will say what moved and that we cannot prove the cause.
The company in numbers, including the one that is zero.
Every number here comes from a record with a date: the app's git history, the decision log in our product spec, the docs on this site and our own run. None of them is a customer number, because we do not have customers yet.
- 31 Aug to 11 Oct: quiet. Two commits in six weeks. Work restarted from a new written plan, our product spec v2, approved on 17 Oct.
- Week of 12 Oct: 181 commits, the busiest week so far, as the product spec v2 and the new design landed.
A short timeline, only from records.
Dates come from the git log, the decision log and the run record. Where we changed our minds, the old idea stays on the list.
-
First commit
The product strategy and the first product spec went in on day one.
-
Billing written as credits
One credit per keyword processed. We later threw this out for one flat plan with no keyword fee.
-
The engine
436 commits in six weeks: the pipeline that reads the top 10, keyword grouping, imports, the review queue and junk keywords.
- 31 Aug to 11 Oct 2026: quiet. Two commits in six weeks.
-
Product spec v2 approvedDecision
With 33 founder decisions that day, among them one plan in three price bands, locked for life (D-18).
-
Page reading moved onto our accountDecision
You no longer need a key of your own for it. SerpDad pays for it inside the plan (D-39).
-
Run 2 approved on serpdad.com
1,797 keywords, estimated at $4.32 to $14.77, billed $13.10.
-
This website, rebuilt
With the copy rules on this page enforced as tests.
Eight reasons SerpDad might be wrong for you.
I would rather lose you here than after you have set up two provider keys. Each reason links to the page that explains it.
- You want a tool that publishes for you.
SerpDad never presses Publish. Drafts land in WordPress, Webflow, Shopify or Google Docs as drafts. Why
- You want a keyword database.
It is not one. Bring keywords from Ahrefs, Semrush, Search Console or a CSV, and SerpDad turns them into a page plan. How the plan works
- You want to track ChatGPT or Perplexity answers.
AI visibility covers Google AI Overviews and AI Mode only. What it tracks
- You do not want to create provider keys.
Every run uses your own DataForSEO and AI accounts. That is ten minutes of setup, and it is how we avoid a markup. Bring your own keys
- You want a score that predicts rank.
Our content score is advice from 0 to 100. It is never a gate and never a forecast. The content score
- Your buyers search outside the United States.
Plans read Google's results for the United States, in English, on desktop. Other markets are not built yet.
- Your security review needs SOC 2 today.
We do not have a SOC 2 report or an ISO certification. What we do have
- You want a big, settled vendor.
SerpDad is a small company with zero customers today. If that is a deal breaker, it is a fair one.
How we work, in public.
Decisions are numbered and dated. When I settle an open question in the product spec, it gets a number, a date and the requirements it changes. There are 42 so far. The roadmap shows the ones that change what you can use.
We run SerpDad on our own site first. The build log shows our runs, what they cost and what we would change, before we ask anyone else to trust a run.
Copy rules are tests. This website fails its own build if a page uses a dash, promises a ranking, or targets a keyword our own SEO plan gives to a different page. How that works
Mistakes go on the changelog. If we break one of our refusals, the fix and the date go on the changelog.
Where you may have heard me.
Odys Talks: search engine abuse or entrepreneurship, a live conversation.
Matt Diggity: with the owners of a site that made $800k in two months.
Holly Starks: affiliate marketing and the Conch House story.
I also organise The SEO Event and write Missing Intent. Find me on LinkedIn and X.
He reads leaked documentation for fun. I read the top 10. We get along.
A hard question before you sign up?
Email the founder.
Write to [email protected]. It reaches the people who build SerpDad, and I would rather hear the hard question now than after you pay.