01default
Suggest
The engine proposes, you approve each item. The default for every new blog.
How it works
From a stale post to a published rewrite that ranks.
FOXQUILL runs a closed loop on every blog in your network. It finds what is slipping from real Search Console data, fixes it with grounded, voice-matched writing, verifies quality before anything ships, and measures whether the change actually worked.
Opportunity
Best budget tents
position 43 - 167 impressions
Rewrite
Grounded, voice-matched
real facts, cited - 0 placeholders
QA gate
Publication-ready
voice 8.5 - all checks passed
Publishedlive
WordPress revision
one-click rollback
Uplift after publish
+18% clicks
The walkthrough
Follow one post through the engine
Below, a demo bakery blog's “Why is my sourdough crumb dense?” goes from underperformer to published rewrite. At every step you see the same thing the operator sees.
Understand the network
FOXQUILL mirrors every post from WordPress and pulls up to 16 months of Search Console history per URL, plus Bing Webmaster data where connected. Each post is embedded into a shared vector index, so the engine knows what you have and how every page actually performs.
- Full inventory sync per blog
- Clicks, impressions, CTR, and position by query
- Vector index for internal linking and cannibalization
Score and diagnose
Every page is scored from real signal, not guesses: striking distance, low CTR, decay, query gaps, cannibalization. Each underperformer gets a plain-words diagnosis that cites its own numbers and lands in one clear action.
- Opportunities ranked by priority
- Each diagnosis cites its numbers
- Triaged: quick win, rewrite, consolidate, or retire
Research the facts
Before writing, the engine researches the real facts the page needs from live web sources and keeps only the ones whose values appear in the fetched source. A claim that cannot be sourced is written qualitatively or dropped - never invented.
- Real facts from real pages, validated
- No fabricated statistics, ever
- Unsourced claims stay qualitative
Write in the locked voice
The rewrite is answer-first and built for AI search: question headings, a real FAQ, comparison tables where they fit, fresh schema, a visible last-updated date, and internal links both ways - all in the blog's approved, locked voice.
- Answer-first structure for AI Overviews
- BlogPosting + FAQ + Breadcrumb JSON-LD
- Two-way internal links from the vector index
Verify before it ships
A two-layer QA gate checks every draft: deterministic linters first (house style, structure, grounding, metadata), then AI judges score voice against the locked anchors, answer-first quality, and fact attribution. A draft that misses is improved or regenerated until it passes - or flagged for you, never auto-published.
- Zero placeholders, zero fabricated stats to pass
- Voice scored against the locked anchors
- Images generated only for drafts that pass
Publish reversibly, then prove it
You approve one at a time, in bulk, or on a schedule that spreads publishes over days. Every write lands as a reversible WordPress revision. Two weeks later the engine measures the result against that page's own baseline, records the win or loss, and requeues anything that slipped.
- Every write is a one-click rollback
- Uplift measured against the pre-change baseline
- Pages that decline re-enter the queue automatically
Your throttle
How much runs on its own is a dial, not a default
Every blog starts at Suggest. Higher levels are earned with measured wins on that blog, never assumed - and whatever the level, every write stays a reversible revision.
02
Auto-draft
Drafts and revisions are prepared in bulk; you approve in batches, or schedule them across the week.
03earned
Guarded publish
Ships on its own under hard rails - earned only after measured uplift on that blog, and every write stays reversible.
The workspace
You stay in control the whole way
Every draft arrives in one queue with its scores. Approve and publish, schedule a batch across the week, send a near-miss back for one focused improvement pass, or reject it.
Questions
Before you connect a blog
What do I need to connect?
A WordPress site and its Google Search Console property. WordPress connects with an application password, Search Console with a Google sign-in. Bing Webmaster is optional per blog. After the first sync and performance pull, the first opportunities appear on their own.
How long before I see results?
The queue fills within the first day. Search itself moves slower: every published change gets a two-week settle, then is measured against that page's own pre-change baseline and recorded as a win, a loss, or flat. No invented projections - you see real deltas per page.
What happens if a rewrite makes a page worse?
It is caught, not buried. The loss is recorded, the page goes back into the fix queue automatically, and because every write is a WordPress revision, restoring the previous version is one click.
How much runs without me?
Your call, per blog. Suggest mode approves nothing without you. Auto-draft prepares drafts in bulk for batch review. Guarded publish ships on its own under hard rails, and only unlocks after the engine has proven measured uplift on that blog.
See it on your own blog
Tell us about your network, connect a WordPress site and its Search Console, and watch the first opportunities appear.