Uncategorized

LevelUpStats Connector Troubleshooting

◷ 3 min read ⚡ May 11, 2026 👤 314media

That screenshot means Level Up is not actually reading the live WordPress page yet — so verification is failing before it can compare the title/meta.

The biggest red flag is the circled field:

Connector Base: blank

That should probably be the connected WordPress site / REST connector base URL. Since it is empty, the app does not know where to ask the WordPress connector for the live SEO values.

So this is not saying the title/meta are wrong. It is saying:

“I cannot reach or resolve the WordPress connector/page, so I cannot read the live title tag or meta description.”

What each field means

Title Tag: Unreadable
Level Up tried to read the live page title but failed.

Meta Description: Unreadable
Same problem for meta description.

Connector Base: blank
The app has no stored connector endpoint/base URL for this site/account/mission. This is likely the real blocker.

Draft Source: completion_notes.locked_seo_snippet
The recommended SEO snippet came from the mission/completion notes. That part is fine.

Read Error: None
Bad UX/debugging. It failed, but did not capture a useful error message.

Resolved Post: Not resolved
The system could not match the mission URL to a WordPress post/page ID. That can happen if the connector base is missing, the URL does not match the WP site URL exactly, or the connector lookup endpoint failed.

Quick things to check

  1. In the Level Up app, confirm this site still shows as WordPress connector connected.
  2. In WordPress, open the Level Up connector plugin screen and make sure it shows connected/checking in.
  3. Confirm the mission URL belongs to the same exact domain connected in Level Up:
    • https://example.com/page/
    • vs https://www.example.com/page/
    • vs staging/dev URL
      These mismatches can break post resolution.
  4. Re-save WordPress permalinks.
  5. Clear cache/CDN if title/meta were just changed.
  6. Try opening the page in an incognito browser and view source. Make sure the expected title/meta are actually in the rendered HTML.

Likely app-side bug

The app should not be showing this vague verification screen. It should fail earlier with something like:

“WordPress connector base URL is missing. Reconnect the WordPress plugin before verification.”

And it should probably have fallback logic:

  1. If connector_base is blank, derive it from the connected site URL.
  2. If post ID is not already stored, resolve the post by URL path through the connector.
  3. If the connector cannot read Rank Math/Yoast/native meta, fall back to reading the public page HTML.
  4. Save the real error instead of showing Read Error: None.

So the immediate issue is probably not the SEO mission itself — it is the connector/site mapping for this mission.

Upload the latest build and I’ll make a patch that fixes the verification flow and gives a much clearer error when connector base or post resolution fails.

Scroll to Top