Connecting Google Search Console
Connect your blog to Google Search Console to accelerate indexing, track performance, and unlock sitemap submission and ranking data.
Connecting your blog to Google Search Console is essential for accelerating indexing and accessing performance data. This guide walks through the verification process to enable sitemap submission and ranking tracking.
Before you start
- Google Search Console integration is available on the Team Plan and above, including during the 14-day free trial. It is not available on the Free Plan, and it locks again once a trial ends and the blog converts to the Free Plan.
- Your blog must have a custom domain connected before proceeding.
- The Google account you use to register in Search Console and the account you sign in with inside the inblog dashboard must be the same. A mismatch will cause the integration to fail.
How to Register with Google Search Console
-
Start the Process
- Visit the Google Search Console website and click "Start Now"
-
Add Your Blog URL
- Enter your custom domain (e.g.,
https://blog.example.com) - Include the
https://protocol - Click "Continue"
- Enter your custom domain (e.g.,
-
Select "HTML tag" and Copy It
- From the list of verification methods, choose "HTML tag"
- Copy the entire meta tag provided
Note: The "HTML file upload" method offered by Google is not supported by inblog. You must use the HTML tag method.
-
Paste into inblog
- In your inblog dashboard, go to Settings tab → Code injection
- Paste the copied HTML tag into the Start of
<head>tag input and save
-
Verify in Google Search Console
- Return to Google Search Console and click "Verify"
- If unsuccessful initially, try 2–3 more times
-
Connect in the inblog Dashboard
- When linking Search Console inside inblog, sign in with the same Google account you used to register the property in Search Console
How Many Search Console Properties Do I Need?
If your company website is already registered in Search Console, that property still won't work unless it covers your inblog blog address. For example, if the website property is https://www.example.com/ and the blog lives at blog.example.com, www and blog are different addresses, so the website property alone cannot be connected.
Depending on how your domain is connected, inblog recognizes only the properties below. Any one of them is enough.
| How the domain is connected | Search Console properties you can use |
|---|---|
Subdomain (blog.example.com) | https://blog.example.com URL-prefix propertyor an example.com Domain property |
Subdirectory (example.com/blog) | https://example.com or https://example.com/blog URL-prefix propertyor an example.com Domain property |
Root domain (example.com) | https://example.com or https://www.example.com URL-prefix propertyor an example.com Domain property |
- With a subdomain connection, keeping a separate property for your website and for your blog is normal. Seeing two properties in Search Console is not a problem — each one reports only the data for its own address.
- If you would rather have a single property, create an
example.comDomain property (the type verified through DNS). A Domain property covers every subdomain, includingwwwandblog, so your website and blog appear under one property. - With a subdirectory connection, your existing website property is enough on its own, because the blog's data is already included in it. Add
https://example.com/blogas a URL-prefix property only if you want to analyze the blog separately — having two properties in that case is also normal.
Troubleshooting: When the Connection Fails
If you reached the "Verify" step in Search Console but the inblog dashboard still shows the connection as failed — or you land on a Something went wrong — There was an issue during the connection process. Please go back and try again. screen during the connection — check the following in order.
- If you just registered it, wait a few minutes and try again. Right after you add the URL in Search Console and save the HTML tag, Google's ownership-verification servers may still be processing. In that case nothing is wrong with your code or settings — Google simply hasn't propagated the change yet, so retry the connection after a few minutes.
- Confirm you're on the Team Plan or above. Search Console integration is available only on the Team Plan and above, including during the 14-day free trial. Once a trial ends and the blog converts to the Free Plan, the integration card locks again.
- Confirm the URL matches exactly. The property registered in Search Console must match the custom domain connected in inblog exactly, including the
https://protocol and the subdomain/subdirectory form. - Confirm the Google account is the same. The account that registered the property in Search Console and the account you sign in with when linking inside inblog must be identical.
- Use only the "HTML tag" verification method. Google's "HTML file upload" method is not supported by inblog.
- Confirm that ownership verification actually completed. The error above can also come from a later step — not the Google sign-in itself, but the step where inblog looks for a verified Search Console property matching your connected domain. Open your public blog page and view the source (Windows
Ctrl + U/ MacCmd + Option + U) to check whether thegoogle-site-verificationtag is present. If it isn't, the HTML tag you pasted in step 4 of "How to Register with Google Search Console" hasn't been saved or published yet — save the tag again, complete "Verify" in Search Console, then retry the connection. - Confirm your permission level on the property. Even with the correct account, a read-only Restricted user role may get past the connection itself but then fail on sitemap submission or data lookups. Check under
Settings → Users and permissionsin Search Console that the Google account you sign in with is an Owner or Full user on that property. This most often trips up people who were merely invited to a property someone else created, or one verified through DNS.
Key Benefits
The integration provides two critical advantages: it "helps accelerate the indexing of your blog and posts" and enables you to track indexing status plus Google search rankings directly in your inblog dashboard.
Last updated 2026-09-03