From zero to indexed: how we drafted and shipped our first SEO article in under 30 minutes
TL;DR
We used CiteClip on our own dogfooding SaaS to research 4 competitors, run gap analysis, draft a 1,600-word article with TL;DR + FAQ + JSON-LD schema, and ship it to WordPress via one-click publish. Total elapsed time: 27 minutes. Total human effort: reviewing the draft and typing a Publish confirmation. Here's what the pipeline did automatically, where it needed a nudge, and what the first-week GSC data looked like.
Every SEO tool demo you've seen ends with a shiny outline and "and then just write the article!"
This post is the opposite: the actual output, the actual keystrokes, and the actual GSC impressions.
If you're a solo founder trying to decide whether AI can replace a content team of one, this is the honest version of that answer.
The setup: 4 competitors, 4 sources, zero backlog
Onboarding auto-discovered 4 direct competitors in 90 seconds. Sources polled within seconds of discovery, not hours.
We ran CiteClip against our dogfood bulk URL status-code checker SaaS.
The auto-discover pipeline then found 4 content sources (blog RSS feeds and sitemaps) and immediately queued the first poll.
The pipeline in order: discover → index → gap → draft
3 min to first competitor posts indexed. 6 min to 47 rows. Gap analysis at the 20-post threshold. 14 topic candidates. Draft: 4 minutes.
- 1Minute 3:
competitor_postshad 12 rows. - 2Minute 6: 47 rows across the 4 blogs.
- 3Gap analysis fires at the 20-post threshold: cross-references those posts against the 25 indexed pages of our dogfood site, produces 14 topic suggestions where competitors ranked and we didn't.
- 4Strongest candidate: "bulk redirect chain checker", specific query with real search volume where BrokenLinkCheck and Dr. Link Check both had blog coverage and we had none.
- 5We picked it. Article drafter: 4 minutes to produce a 1,600-word MDX file with TL;DR block up top, FAQ at the bottom, complete
Article+FAQPageJSON-LD schema in the head.
What the AI got right (and what needed a human)
Keyword placement + internal links + FAQ questions + schema: all correct out of the box. Intro paragraph + one narrow FAQ question needed a human pass.
Option A
Correct out of the box
- Primary keyword placement (H1, first paragraph, meta description).
- Internal-link suggestions: three links back to the tool page in natural places.
- FAQ questions: all matched real PAA entries per the SERP.
- Schema markup: valid
Article+FAQPageJSON-LD. - Tone: plain text, no jargon, no marketing fluff.
Option B
Needed a human pass
- Intro paragraph felt slightly generic, we tightened it to reference a specific customer pain we'd heard from users.
- One FAQ question was too narrow ("does the tool handle IPv6 domains?"), swapped for a broader "how does bulk redirect checking differ from single-URL testing?" which the SERP wanted more.
The publish: WordPress plugin, one click
Signed REST endpoint at /wp-json/citeclip/v1/publish. 3.4 seconds from Publish click to reviewable Draft in WP with schema injected via wp_head.
We'd installed the CiteClip Publisher plugin on the WordPress site during onboarding. The plugin exposes a signed REST endpoint at /wp-json/citeclip/v1/publish.
When we clicked Publish on the drafted article, CiteClip POSTed the markdown-converted-to-HTML payload plus the JSON-LD schema to that endpoint. The plugin created a Draft post in WordPress with the schema injected into <head> via wp_head.
First-week GSC data
Day 6: position 47 (invisible). Day 10: position 31. Day 14 after 2 backlinks: position 18, first click, 89 impressions.
Three days after publish, the URL landed in Google Search Console.
- Day 6: 4 impressions on the target query at avg position 47. Not a win, position 47 is basically invisible.
- Day 10: 12 impressions, avg position 31 (still page 3, but a meaningful move for a brand-new URL with zero backlinks).
- Day 6 (same day): we submitted the URL to IndieHackers Show & Tell and to a subreddit where "bulk URL tools" comes up. Two backlinks in one day.
- Day 14: 89 impressions, position 18, first click.
The uncomfortable takeaway
AI compresses drafting from 6 hours to 30 minutes. It does NOT compress distribution. Without the day-6 backlinks the article stays at position 47.
The article is the easy part. AI drafting compresses what used to be a 6-hour research + write cycle into a 30-minute review + edit cycle.
CiteClip's next milestone (Q3 2026) is a distribution assistant that handles that piece automatically. For now, we tell every operator: draft with CiteClip, publish with one click, then spend 15 minutes cross-posting.
What we're going to try next
Same playbook, 5 more topics from the gap-analysis queue over 10 days. Follow-up post with 30-day GSC + MRR data.
Same playbook, five more topics from the gap-analysis queue over the next 10 days. Then we'll publish a follow-up post with the full 30-day GSC results and MRR attribution from the tracking pixel.
If you want to run the same experiment on your own SaaS, sign up at citeclip.com. The first 4 articles are free and no credit card is required to start.
Frequently asked
How long does it take to publish an SEO article with CiteClip?
Does CiteClip publish to WordPress?
/wp-json/citeclip/v1/publish. Clicking Publish in CiteClip POSTs the markdown-converted-to-HTML payload plus JSON-LD schema (Article + FAQPage) to that endpoint, which creates a Draft post in WordPress with schema injected into <head> via wp_head. Total elapsed time: 3.4 seconds.