Troubleshoot publishing and measurement

Find the symptom, read the cause, apply the fix. Everything here is about the connected half of the loop; drafting, scheduling, and the calendar need no integration at all and fail for other reasons.

Symptom	Most likely cause	Fix
A publish fails with “No active binding”	Nothing is connected and activated for that channel	Publishing
An analytics binding fails to verify	The G- measurement ID was used where the numeric property ID belongs	Analytics
Search Console answers 403 on every call	The property is entered in a form you do not own	Search Console
The search columns on a new article stay empty	The page is not indexed yet, and reporting lags behind that	Search data

A publish fails with “No active binding”

Publishing runs through a binding that a person has verified and activated, so there is nothing to publish into until one exists. The message names the operation it wanted, as in No active binding for cms.post.publish.

Import the provider in Settings, then Integrations, create a connection, then verify and activate the binding on the Categories tab. The setup pages cover each one: a CMS, analytics, Search Console, and social platforms.

Two related messages mean something different, and both are about which binding applies rather than whether one exists:

• “No active binding … applies to this input.” Bindings are active, but each is limited to certain inputs and none covers this one. The message lists what each is limited to.
• “N active bindings … apply to this input.” Two routes claim the same publish, and picking either would be a coin flip on something the public sees. Disable the ones that overlap so exactly one applies.

You can also skip publishing entirely: post from your own account and record the numbers by hand.

Verifying analytics fails on the property ID

The connection holds the G- measurement ID from your site’s page tag, and the reporting API accepts only the numeric property ID. The form cannot tell the two apart, so the mistake is accepted quietly and surfaces at verify as Google’s own answer: Invalid property ID, followed by A numeric Property ID is required.

Find the number in Google Analytics under Admin, then Property Settings, replace the G- value in the connection settings, and verify again. See two IDs, and only one of them works.

Search Console answers 403

A Domain property and a URL-prefix property are two different properties, and both spellings are valid forms, so the form accepts either. If you own sc-domain:example.com and entered https://example.com/, every call comes back 403 saying the user does not have sufficient permission for that site. It reads like an account problem and it is a spelling problem.

Open Search Console, copy the spelling from the property picker character for character, and paste that. Check too that the Google account you authorized with can see the property: Restricted access or better is enough, since the connection only reads. See two kinds of property, two spellings.

Search data never appears

Two waits stack before an article’s first search number, and neither is a fault. Google has to index the page, which can happen inside a day from a submitted sitemap and can take weeks on a new site with few inbound links. Search Console’s own reporting then lags a further two to three days.

While you wait, the surface keeps the two states apart: an empty cell means nothing has landed yet, and a zero means a zero was collected. If the property answers nothing at all rather than zeros, the spelling problem above is the likelier cause.

For an article published before the connection existed, the past is recoverable. Backfill history on the content view pulls daily readings as far back as the provider holds them, roughly sixteen months for Search Console.

Next steps

• Metrics and attribution: what every number means, and when it appears.
• Publish an article: the whole path, from draft to measured.
• Common issues: symptoms outside marketing.