blogr.ai Search Console Keyword Intake and Title Approval (Onboarding)
A sequence with 8 steps: Connect the client's Google Search Console property inside blogr.ai.
By InnovaAI ResearchPublished
What are the steps?
blogr.ai Search Console Keyword Intake and Title Approval (Onboarding)
- 01
Connect the client's Google Search Console property inside blogr.ai
Use the Search Console connection screen to authorize the property that matches the client's live domain. Confirm the property returns impression and position data before moving on; a property with no impressions will produce no keyword proposals and the account will sit idle.
- 02
Attach the publishing destination (WordPress, Webflow, Shopify, Ghost, or webhook)
Pick the CMS the client actually publishes on. If the client runs a custom stack, use the webhook destination so articles land in their pipeline rather than a staging site nobody checks.
- 03
Enter focus topics, audience, and brand voice in the onboarding fields
This is the only place blogr.ai learns the client's tone. Pull three to five existing client pages the client is proud of and mirror that register in the voice description. Vague voice input produces generic drafts that the agency will rewrite anyway, which defeats the retainer.
- 04
Review the topical map blogr.ai builds from real search demand
The map groups pillar pages with supporting articles. Check that pillar topics match the client's commercial priorities, not just whatever keywords have volume. Remove pillars the client cannot credibly write about.
- 05
Approve or reject proposed article titles before any drafting begins
Keep manual title approval on. Auto Publish skips this gate, and on a new client account the first month of titles is where misalignment shows up. Reject titles that drift off the topical map and the next proposal round adjusts.
- 06
Set the monthly article ceiling against the plan tier
Solo allows 10 articles a month on 1 website, Starter allows 25 articles pooled across 3 websites, and the Agency plan reaches 200 a month. Match the ceiling to what the client's approval capacity can absorb, since unapproved drafts do not publish.
- 07
Confirm the first published article carries cover image, FAQ, schema markup, internal links, and cited sources
Spot-check one live post in the client's CMS. If schema or internal links are missing, the publishing connection is misconfigured and every subsequent article inherits the fault.
- 08
Schedule the Search Console ranking review for 30 days after first publish
blogr.ai tracks position and impression movement per article and surfaces refresh suggestions. Book the review into the retainer calendar so the agency reports movement on published URLs rather than article count.
More on blogr.ai
- StrategyWhy blogr.ai Turns Search Console Data Into a Retainer Agencies Can Defend
- Conceptblogr.ai Approval Gate Economics
- Evaluation Ruleblogr.ai Rule: Adopt Only When Search Console Already Holds the Demand
- Decision Frameworkblogr.ai: Buy vs Skip (Agency Content Retainer Decision)
- Failure PatternThe blogr.ai Approval Queue Trap: Why Agencies Fail With blogr.ai in Multi-Client Content Retainers
- Implementation Blueprintblogr.ai Local SEO Content Retainer (5-7 days)