---
title: "Troubleshooting"
description: "The problems that come up most often, and the check that resolves each one fastest."
updated: "2026-08-28"
verifiedAgainst:
  - packages/shared/src/autopilot.ts
  - packages/shared/src/domains.ts
  - packages/shared/src/project-lifecycle.ts
  - apps/web/lib/server/bootstrap-security.ts
  - apps/web/lib/server/workspace-invitation-service.ts
---

Grouped by what you are seeing.

## Nothing is being published

Work through [when a run stalls](/autopilot/troubleshooting). In order: is
Autopilot activated for **this** Project, is its status active, is the Project
archived, are there approved Topics, is there allowance left, are posts sitting
at an approval gate, and is billing in order.

## Posts are produced but never go live

That is Assisted mode, or Content Directions set to `review`. Both are working
as configured. See [modes](/autopilot/modes) and
[Content Directions](/content/directions).

## The setting I changed did nothing

Check the Project switcher. Settings pages look identical across Projects, and
almost everything in Blogged is scoped to the active Project.

## My custom domain will not verify

<PropertyList>
  <Property name="Wrong record type">
    It must be a CNAME, not an A record.
  </Property>
  <Property name="Apex domain">
    `yourcompany.com` cannot work. Use `blog.yourcompany.com`. See
    [custom domains](/blog/custom-domain).
  </Property>
  <Property name="Proxy enabled">
    A proxying DNS provider has to be set to DNS only for verification.
  </Property>
  <Property name="Conflicting record">
    Another record on the same name will block it.
  </Property>
</PropertyList>

## The website scan did not finish

Some sites cannot be read: a login wall, an aggressive bot filter, or a page that
renders entirely after an interaction. Write a description and upload files
instead. Both count as evidence. See [Sources](/onboarding/sources).

## Posts are published but not indexed

Indexing is Google's decision and takes time on a new domain. Connect
[Search Console](/analytics/search-console), confirm the sitemap was submitted,
and read [indexing and coverage](/analytics/indexing).

## A draft says something wrong about my product

Correct the fact in the Knowledge Engine rather than only fixing the article. A
fact you confirm yourself outranks a crawled one, and it stops the same sentence
reappearing in the next draft. See [verification](/knowledge/verification).

## Generated images do not look like my product

Approve real screenshots in [Assets](/assets/review) and enable reference guided
generation. See [generated images](/assets/generation).

## I am being asked to verify an email address I already verified

You changed the address on your account. Verification is checked continuously on
a Free Project, not only at signup, so a new address is unverified until you
click its link and drafting, images and topics are refused in the meantime.
Nothing is lost. See [Sources](/onboarding/sources).

If signup itself never completed, check that your browser is not blocking site
storage for Blogged: Free signup needs to store one identifier, and a browser
that refuses cannot claim the grant.

## My teammate never got the invitation

Check these in order.

<PropertyList>
  <Property name="The sending domain">
    Invitations come from `invites.blogged.dev`, not from the domain your billing
    email uses. Search for that, including in spam, and allow it.
  </Property>
  <Property name="The address it went to">
    An invitation can only be accepted while signed in with the exact address it
    was sent to. A different address on the same person will not work.
  </Property>
  <Property name="Seven days">
    Links expire after seven days and work once. Send a new one rather than
    forwarding the old message.
  </Property>
  <Property name="A daily cap">
    Any single recipient can receive five invitations a day across all of Blogged,
    and a workspace can send 100. Resending the same one has a 60 second cooldown.
  </Property>
</PropertyList>

If sending was refused rather than delivered, the message says which check
stopped it. See [roles and access](/workspaces/roles).

## Still stuck

[hello@blogged.dev](mailto:hello@blogged.dev), with the Project name and what you
expected to happen.