Hosting and permissions
Find the connection your website can support.
The right installation depends on how your pages are published. Confirm the available access before treating any platform name as a completed integration.
Start with the publishing route
| Your website | What must be possible | What to check first |
|---|---|---|
| Static HTML or generated output | The publishing process can map public URLs to the HTML files that should change. | Who can deploy those files, preserve a backup and check the public result? |
| Node or server-rendered application | An authorized server-side integration can be installed in the application. | Can your developer change the server or rendering process on this hosting plan? |
| CMS or hosted website builder | The platform permits a suitable plugin, publishing API, build step or other authorized server-side route. | Which access does your actual plan provide? A platform name alone does not establish that a route is available. |
Published website-side clients cover Node and static publishing routes. Other platform categories have installation guidance that must be adapted to the actual site. For a CMS or hosted platform, your developer must confirm the permitted route for the installed version and hosting plan.
Reporting access has a different purpose
| Service | Why you connect it | Customer setup |
|---|---|---|
| Google Search Console | Search impressions, clicks and the other observations available for your property. | Authorize the correct account and select the verified website property. |
| Google Analytics | Available visitor and page measurements from a GA4 property. | Select the matching property and check that its intended tracking tag is already collecting data. |
| Bing Webmaster Tools | Search and page-performance information available for your verified website. | Verify the site in Bing and configure its connection in the portal. |
| IndexNow | Notify participating engines about eligible changed URLs. | Install the supplied verification file. A notification receipt does not establish that a URL was indexed. |
Keep these permissions separate
A read-only reporting connection does not authorize page updates. A browser widget does not provide server publishing access. And authorizing a GA4 property does not install its tracking tag.
Use the portal to check both connection status and whether measurements were actually returned. A newly connected service can have no data yet; that should remain visible as missing data.
Bring the instructions to your developer
Copy the instructions for the exact website from the portal. They cover ownership, protected credentials, the supported installation route and checking the public result. The website integration guide provides the detailed installation contract.
Review my connections