HELP AND DIAGNOSIS
Troubleshooting
Start with the exact message and follow the request path: account, property, integration, network and finally content.
Empty Google data
Confirm the authorized account can access the property, the URL matches protocol and subdomain, and initial sync has finished.
If GSC has data but GA4 does not, check the Analytics property, measurement ID and event configuration.
WordPress returns 403 or does not respond
Confirm the plugin is active and the API key belongs to the site. If the request does not reach WordPress, review CDN, WAF, firewall and rate limits with the host.
For a limited exception guide, see the CDN and firewall section in WordPress Bridge.
The extension does not connect
Verify the token is active, the extension has permission for the page and the tab was refreshed after changing URL. If it persists, revoke and create another token.
Also check that the browser allows Chromium extensions and that no corporate policy blocks it.
GitHub does not show a file
Confirm repository, branch, path and permissions. If content comes from another repository or CMS, verify which source actually reaches production.
Do not test directly on the production branch when the team uses pull requests and checks.
Before opening an issue
Share the minimum context needed to reproduce the problem and remove secrets from every sample.
- Include project, feature and approximate time.
- Copy the exact error code and message.
- Describe steps to reproduce it.
- Include the affected URL and browser or integration.
- Hide tokens, API keys, cookies and private data.