SEO Dispatcher helps you move from “we should improve SEO” to a specific change you can review and publish. The workflow begins with your website, not a blank writing box.
You can use it to inspect a site, connect search data, choose a relevant content task, prepare an article, and send the approved file through GitHub. You do not need to complete every setup step on the first day.
Here is the practical order.
1. Add the website you want to improve
Start with the public production URL. Use the preferred version of the domain—the same version you want in canonical links and the sitemap.
SEO Dispatcher reads the accessible site to build context about the product, audience, features, and existing content. Review that profile before relying on it. A website can be vague, outdated, or incomplete, and the app should not be treated as knowing facts that the site never provided.
If the website is still private or only available on your computer, publish a safe preview or wait until the relevant pages are accessible. Do not paste secrets or private customer information into the website description.
2. Run the SEO audit
The audit looks for different kinds of work, including technical issues, page structure, content quality, internal links, performance data when available, and index information when Search Console is connected.
Begin with confirmed critical issues. A blocked page, broken canonical, or inaccessible important URL usually deserves attention before another blog post.
Treat warnings as questions to investigate. A long title is not automatically a bad title. A page with few links may be perfectly complete. Open the evidence, inspect the live page, and decide whether the finding affects users or search engines.
The Overview page summarizes the latest audit, indexable pages, search performance, drafts, and publishing state so you can see the next useful action without opening every part of the app.
3. Connect Search Console when you have data
Search Console adds evidence about how Google currently sees the website. Connect the Google account that has access to the correct property, then bind that property to the website in SEO Dispatcher.
Use it to answer questions such as:
- Which pages receive impressions?
- Which searches show a particular page?
- Does a query match the page's real purpose?
- Is an old article losing relevant visibility?
- Is a new page beginning to appear for the intended topic?
An impression is not a customer, and a click is not a conversion. Use analytics, enquiries, trials, or sales data separately when judging business results.
If the website is new and has no Search Console history, continue with customer questions, support conversations, and the product's real use cases. Mark demand assumptions as assumptions.
4. Choose between fixing a page and writing a new one
Do not create a new article simply because you found a keyword.
Open the content library and check whether an existing page already answers the question. Improve that page when its purpose is right but the answer is weak, old, unclear, or incomplete.
Create a new article when the reader has a distinct problem that no current page serves. Keep the intent clear:
- Informational: the reader wants to understand something.
- Commercial: the reader is comparing approaches or products.
- Transactional: the reader wants to complete a task or take action.
- Navigational: the reader wants help with a particular product or destination.
The format should follow the intent. A buyer comparing tools needs evaluation criteria and trade-offs. Someone trying to add a blog needs ordered setup steps. Turning both into generic “ultimate guides” makes them less useful.
5. Review the proposed topic and brief
Topic ideas should connect a real reader problem to something the website can credibly help with. Reject an idea when the connection relies on a stray word or an invented feature.
Before generating an article, check the brief:
- Who is the reader?
- What are they trying to decide or do?
- What should the article answer?
- Which product facts are supported?
- Which existing pages should be linked?
- What would be a natural next step?
Change the brief if the answer is unclear. A better brief is more valuable than another round of decorative rewriting.
6. Generate and edit the draft
SEO Dispatcher prepares the article using the website context, selected topic, research available to the workflow, and the site's content format.
Read the draft as an editor, not as someone approving a machine score. Check every product claim, instruction, example, link, and comparison. Add details only your team knows. Remove generic sections that do not help the reader finish the job.
The SEO review separates measurable text checks from editorial judgment. Counts such as words, links, or repeated paragraphs can reveal possible problems, but they do not prove that an article is useful or will rank.
Use the editor to revise the article until the title, opening, sections, and CTA all serve the same intent.
7. Connect GitHub when the draft is ready
GitHub is needed for publishing, not for understanding the website or drafting the first article.
Choose the repository and branch used by the website. Review the detected content folder, file extension, and frontmatter. If the site already has a blog, follow its current structure. If it does not, review the proposed blog scaffold carefully because it changes more than one file.
For a pull request, check the diff before merging. For a direct commit, use it only when your team is comfortable with that publishing path. In both cases, the website's own hosting process performs the deployment.
8. Confirm the page is live and measure the right thing
Publishing a file is not the same as publishing a working page.
After deployment, confirm that the URL loads and contains the intended metadata and content. Check the canonical, sitemap entry, internal links, images, and mobile layout. If you use IndexNow or submit a sitemap to Google, do that only after the public URL exists.
Then allow enough time for meaningful data. Return to the page in Search Console and inspect the searches it appears for. Look for relevance before volume.
If the wrong audience finds the page, revisit its purpose and wording. If the right audience reads it but does not take the next step, examine the offer, CTA, and fit between the article and the product. Do not assume every disappointing result is a keyword problem.
A simple first session
If you want to try SEO Dispatcher without setting up everything at once:
- Add one website.
- Review its profile.
- Run the SEO audit.
- Pick one confirmed issue or well-supported content gap.
- Prepare one change.
- Review it yourself.
- Connect GitHub only when you are ready to publish.
That is enough to judge whether the workflow helps. The goal is not to fill a dashboard. It is to make one useful improvement to the real website.