404 to a reader and rest_forbidden to the API. Their own posts load fine,
so their site is healthy. Our database calls all three "published".push-generate-posts.ts:434 hardcodes https://{domain}/wp-json{route} for
every non-local domain. There is no ?rest_route= fallback./wp-json/ 404s. I re-tested it today. Every
backend push to this site fails.post-puller.php:161 sets
$post_status = 'draft' unconditionally, commented "insert as draft for the customer to
review and publish".trialController.ts:634 writes
status: 'published' unconditionally and clears generation_error.pull_claimed_at, which is the proof this was the pull path.published. I probed all 77:
23 are invisible drafts on 8 sites, 44 are genuinely live (those customers found and published
them by hand), 1 was deleted, 9 I could not reach.
| Site | Invisible drafts |
|---|---|
| dotifi.com | 9 |
| fahsignatureclinique.ca (paying) | 3 |
| mpmlaspowertv.com | 3 |
| yello.ng | 2 |
| www.wordpressaitools.com | 2 |
| wacofirsthomebuyers.com | 2 |
| prolinecheshire.co.uk | 1 |
| sanchaykaro.com | 1 |
publish_rate_14d.Hi,
Two days into your trial, and I owe you an explanation before anything else.
ClearPost has written three posts for MPMLAS POWER TV, one a day: how to check the Karnataka SSLC and PU results, a guide to Mangaluru civic infrastructure covering water, roads and waste, and the latest on the Pumpwell flyover and city traffic diversions. All three reached your site.
None of them are live. They are sitting in your WordPress as drafts, and that is our fault, not a setting you chose. Your site uses plain permalinks, which switches off the address our publisher writes to. Our plugin caught the posts through a backup route instead, and that route saves everything as a draft. We are fixing it.
Two things put this right today. Open Posts in your WordPress admin and publish the three drafts waiting there. Then open Settings, then Permalinks, choose "Post name" and save. That restores direct publishing, and it will do more for your search traffic than anything else on the site, because your articles currently sit at addresses like /?p=2027.
I opened with the SSLC results guide because that is where the demand is. "Karnataka SSLC results" gets 22,200 searches a month, and a Mangaluru news portal should own that query rather than a national site.
What comes next aims at the part of your site nobody else has, the Know Your Leaders directory. In September the plan covers Mangaluru MLAs and their constituencies, and what MPs, MLAs and corporators are doing week to week.
Is this hitting the mark? If the topics are wrong, or you would rather these ran in Kannada, tell me and I will rebuild the plan.
Christian
MPMLAS POWER TV is a regional news portal for Mangaluru, Dakshina Kannada and Udupi. The name comes from MP and MLA. Its distinctive asset is a Know Your Leaders directory: MP, MLA, MLC, Corporators, GP, TP and ZP Members, Deputy Commissioner, Police Commissioner, Superintendent of Police, Doctors, Educationalists, Engineers, Industrialists, Musicians. No competitor has that.
Three queued posts point straight at it: Mangaluru MLAs and constituencies (09-12), the politics beat on MPs, MLAs and corporators (09-13), and MLA news (09-23). That is the strongest thing in the plan, so the email leads the forward picture with it.
The site last published on 2026-05-23, three months ago. The email does not mention that.
| Claim | Source |
|---|---|
| 3 posts, one a day, no failures | 3 calendar rows with wp_post_id, 0 generation_error |
| None are live | 2060, 2068, 2076 all return 404 on the front end and rest_forbidden on the API |
| Their own posts load fine | 2027 and 2024 both return publish |
| Plain permalinks | Their live post URLs are https://mpmlaspowertv.com/?p=2027 |
/wp-json/ is dead | 404 today. ?rest_route=/ returns 200 with 31 namespaces |
| Karnataka SSLC results 22,200 | DataForSEO, from their own 394-keyword set |
| Ranks for nothing yet | DataForSEO live SERP, 0 ranked keywords |
WordPress keeps resolving ?p=123 after the switch and canonical-redirects it to the
pretty URL, so nothing breaks. For a news site publishing under /?p=, this is the single
biggest on-site SEO change available. It also repairs our push path permanently, which is why it is
in the email rather than only on our fix list.
I could not read the drafts to review their quality. Their MCP endpoint returns
jwt_auth_invalid_token: they run a JWT Auth plugin that intercepts the
Authorization: Bearer header before our permission callback ever runs. Our license key is
not a JWT, so it is rejected with 403. insert-post is unaffected because it authenticates
with X-License-Key. Worth logging separately: MCP is unreachable on any site running
jwt-auth.
isLive keys on our review_before_publish column and never on what the site
actually did. That is a second symptom of the same defect. The email does not confess it directly, but
it does correct it.post-puller draft status and the
markPostCreated hardcoded published are NOT in that PR either. Those are new.