Quickstart
From a new account to a published post, in the order the product asks for it.
Before you start and expected result
Have the product URL or a written product description ready. No card is required: a first Project reaches the Plan step with its Free grant already active.
The Project setup is complete and you know both paths to publishing the first post.
Setting up your first Project is a fixed sequence of ten steps. Each one unlocks the next, so there is no way to get out of order and no way to skip ahead to a step that would not have what it needs.
A second or later Project may not follow this sequence. If your workspace is still running its Free Project, an added paid one short circuits to the plan step and stays there until a billable plan is on it, so payment comes before the website scan. If the workspace is already on a paid subscription, an added Project runs the steps in the ordinary order. Everything below describes a first Project; creating a Project sets out the rest.
Expect the whole sequence to take under an hour of your attention, most of it reviewing rather than typing.
Before you start
You need the URL of the product you are writing about, or enough written description to stand in for it.
The ten steps
- Sources
Give Blogged something to learn your product from: scan your website, write a description, upload files, or any combination. The step completes once there is enough evidence, not once a scan has run, so a product with no public site can still get through it.
- Theme
Review the visual identity picked up from your site and choose the theme your blog will use. This happens early because everything published later inherits it.
- Strategy
Approve the strategy generated from your evidence. Approving it produces your Content Directions, which is what the step is really waiting for.
- Competitors
Approve the competitors Blogged found, add your own, or confirm that you have none to track. Either answer completes the step.
- Plan
Choose how this Project is paid for: a plan, or the one-time Free allowance if your account is eligible for it. Pricing is per Project, so this and any later plan decision is about one Project rather than about your account. See the plan step and Plans.
- Topics
Approve at least one Topic. Topics are the specific articles that will be written, and setup cannot continue past this step until one is approved.
That is a requirement of setup rather than of writing. Once the Project is set up you can also draft from a custom brief or an imported draft, neither of which needs a Topic.
- Calls to action
Review the CTAs that will appear in published posts.
- Lead capture
Review how readers are invited to hand over an email address. This is the last required step: once it is done the Project can be finished.
- Assets
Review the images discovered on your website so drafts can use real product visuals rather than generic ones.
- Autopilot
Decide how the Project runs from here, and activate it if you want it running without you.
Publishing the first post
Once at least one Topic is approved you have two routes to a published article.
Activate Autopilot on the Project. It picks an approved Topic, drafts it, and takes it as far as its Content Direction's approval policy allows. If that Direction requires review, the Post waits for you rather than publishing.
Open Content, then Topics, and generate a Post from an approved Topic directly. You get the same pipeline, run once, on demand. Edit it in the editor and publish when you are happy.
Either way the article lands on your blog at yourname.blogged.dev until you
connect a domain of your own.
What to do next
Serve the blog from your own hostname, with the DNS records and certificate handled for you.
Connect Search ConsoleBring indexing status and search performance into the workspace.
Understand AutopilotThe two automation modes, and which gates each one respects.
Fill the Knowledge EngineThe more grounded facts it holds, the less generic every draft becomes.