Why Isn't My Post Live?
Find out why a Revnu post isn't showing on your site, from a blog that isn't connected or an I've Connected It refusal to posts waiting for approval, a static site that needs a rebuild, DNS still pending, a Failed post, an access error from Revnu's article service or a paused daily post.
A post that isn't live is almost always in one of the states below, and Visibility > Posts tells you which.
Open Visibility > Posts
Open Visibility in the sidebar, then the Posts tab.
Read the status line above the list
It says whether your site is connected and checked. If it isn't, start at state 1.
Read the status next to the post
1. Your site isn't connected yet
The status line above your posts says where setup stands, with one button:
| What it says | What to do |
|---|---|
| Connected, not checked yet (Finish Setup) | Give your developer the API key and setup prompt, deploy, then press I've Connected It |
| Your site hasn't requested any posts from Revnu yet (View Setup) | The integration isn't deployed, or it uses an old key. If you rotated the key, update it on your site and redeploy |
| Checking your site (View) | The check is running. The result lands in your conversation with Revnu. You can leave the page |
| The check found problems (See What Failed) | The fix list is in Review. When it's fixed, press Check Again |
| The check request didn't reach your agent (Ask Again) | Nothing is running. Press Ask Again |
Until the check passes, Revnu doesn't start the daily post. Setup steps: Get Revnu's posts onto your site.
2. I've Connected It says your site hasn't requested any posts
When you press I've Connected It, Revnu first opens your blog address once and waits a few seconds for your site to ask Revnu for its posts. If your site never does, the button is refused straight away with this message:
yourdomain.com/blog hasn't requested any posts from Revnu yet. Deploy the integration with your current key, then check again.
It means your live site hasn't fetched the full post list with your current key. Revnu won't run the check until it has, because it would have nothing to find.
| Cause | Fix |
|---|---|
| The integration isn't deployed yet | Copying the setup prompt isn't enough. Your developer has to build it and deploy it |
| The site uses an old key | Rotating the key in Visibility > Publishing Settings kills the old one at once. Update the key on your site and redeploy |
| The site only asks for some posts | Revnu counts your site as connected when it reads the first page of the full list, with no type or date filter |
| The page is static or cached | A site built before the key was added never asks again until it rebuilds. Rebuild, open any blog page once, then press I've Connected It |
Tip
A test from your developer's laptop with the key also counts as a fetch, so test the deployed site itself, not a local copy. Otherwise the check can start and then find nothing live.
3. The post is waiting for you
Look at the status next to the post:
| Status | What it means | What to do |
|---|---|---|
| Awaiting Approval | Your Blog Posts setting is Ask Me First, or the post is inside its waiting period under Just Do It | Open it and press Approve & Publish to put it live now |
| Your Draft | You wrote it | It publishes the moment you press Approve & Publish |
| Needs Verification | The fact-check flagged claims to look at before it goes live. It never publishes on its own, even under Just Do It | Read the Fact-check panel, fix the claim or ask Revnu to, then approve |
Under Just Do It, a post publishes at 9:00 on the first weekday at least 24 hours after it's ready, so it won't go out at any other time of day. To publish it now, press Approve & Publish. Control what gets published explains both settings.
4. It's published on Revnu but not on your site
The post list shows Not on site yet, and the post editor shows Not on Your Site Yet, instead of Live. That means your site hasn't fetched posts from Revnu since this one was published. Revnu can't put it on your site for you.
Don't delete the post. It's published on Revnu's side, and it appears on your site the next time your site reads the list.
Static site. Live in Revnu means published in Revnu. A static site shows the post only after its next rebuild. Ask whoever deploys your site to rebuild now.
Rebuild hook already set. Revnu called it, but your site didn't pick up the post. Ask your developer to check the hook and the build log. Revnu doesn't retry a hook that fails.
Tip
For a lasting fix on a static site, your developer creates a deploy hook on your host and pastes it under Visibility > Publishing Settings > Content API > Rebuild Hook. Then every publish triggers a rebuild.
5. Your domain is still waiting on DNS
On the hosted blog, Visibility > Publishing Settings reads DNS Pending until your DNS records check out. Compare each record with the card, then press I've Added DNS. Details: The Revnu-hosted blog.
6. No new post today
Revnu writes one post a day on its own. It skips a day when:
Three of its drafts are already waiting for you. Approve, publish or discard one to free a slot. Editing a draft doesn't free it. A post stuck in Needs Verification counts as one of the three, even under Just Do It, so check for those first.
Its recent posts aren't indexed in Google yet, and it's holding off until they are
It chose to improve an existing post instead, which it tells you about
If none of these fits, ask Revnu "why was there no post today?". It has to name the reason.
7. The post says Failed
Failed means the post never finished and was never published. It isn't caused by your site or your setup. One of three things stopped it:
The fact-check found a claim that contradicts your facts. The post is held back rather than published with the claim in it.
The draft used something on your Never Say list. It's held back the same way.
Writing broke on Revnu's side before the post was done.
Revnu is told when a post fails, and it usually fixes the wording or writes a replacement, which shows up in Visibility > Posts with its own status. If a Failed post is still the latest one a day later, nothing else is on its way. Ask in chat: "the post on X failed, please rewrite it."
Warning
You can open a Failed post and publish it yourself with Approve & Publish, but read the Fact-check panel first. The check held it for a reason.
This is different from your site's check failing (state 1), where the fix list is about your pages, not the post.
8. Revnu says its article service rejected the request, or an access error
Sometimes Revnu replies in chat that it couldn't start or prepare a post: its article service rejected the request, it hit an access error, or the post is blocked. If your blog is connected and its check has passed (state 1), that's a fault on Revnu's side. It isn't your file, your blog or your settings.
Try once more
Ask again in a new message. If the post came from a document, paste the text into the chat instead of attaching the PDF.
Email support if it comes back
If the same message comes back, email support@revnu.com. Include the post's topic, the time you saw the message and what Revnu said. Revnu can't file the report for you from chat, so the email is the way to reach a person.
9. Your account is paused
A failed payment or a cancelled plan stops all new posts. Posts already published keep serving. See Payment failed or card declined.
Still stuck?
Ask Revnu in chat: "my latest post isn't on my site, what's wrong?" It checks your live site, not just its own records. If that doesn't settle it, email support@revnu.com with the post's title and your blog's address. More ways to reach a person: Get help.
Frequently Asked Questions
Your site hasn't fetched posts from Revnu since the post was published. On a static site that means it needs a rebuild. Add a rebuild hook under Publishing Settings > Content API so it rebuilds on every publish. Don't delete the post.