Some of the most baffling problems, with blog connectivity, identity, or ownership, can start from simple typographical errors. This possibility will involve both native "blogspot.com" and custom domain URLs.
The Publishing wizard window, in the Blogger dashboard Settings - Basic page, is essential for identifying errors. Whether you paste or type a URL into the registrar's zone editor, the Publishing wizard, or the browser address window, you can make a mistake. Checking the Publishing wizard is as important as examining a Dig log extract - or as viewing an HTTP trace.
Verifying the URLs involved, in the dashboard Publishing wizard, is as important as examining a Dig log extract, or an HTTP trace.
This will be the case, when dealing with various "blogspot.com" connectivity problems, researching a custom domain problem, or a dashboard or ownership problem.
Both screen prints, and text copies, are very useful - and not redundant.
Both a screen print, and a text copy, of the Publishing window (and / or the browser address window) is very useful, when diagnosing connectivity problems - or possibly, researching ownership issues, or similarly vanished blogs. And with a custom domain, similar detail from the registrar zone editor is useful.
A text copy of the contents is needed, to avoid having to re type the URL - and maybe cause a different problem when comparing the URL. And a visual copy of the Publishing wizard is good, to identify the context of any problem.
Let's look at two blogs - and what we need to examine / verify.
My test blog, published as "nitecruzr-test-ssl.blogspot.com".
Here, we see a "blogspot.com" URL, in the browser address window.
Here, we see the Blogger dashboard Settings - Basic page, for a "blogspot.com" published blog.
And the Publishing display, for a "blogspot.com" published blog.
And essential text details, from Publishing, for a "blogspot.com" published blog:
If you are requesting assistance with your native Blogger blog, the latter details, in both a screen print and text copy, will be useful.
My blog, published as "blogging.nitecruzr.net".
Here, we see a custom domain URL, in the browser address window.
Here, we see the Blogger dashboard Settings - Basic page. for a custom domain published blog.
And the Publishing display, for a custom domain published blog.
And essential text details, for a custom domain published blog:
With a custom domain published blog, always click on "Edit", and make a second screen print.
The second page of the Publishing display - which only applies to a custom domain published blog.
You maybe have seen this display, similarly formatted, in an infamous "Error 12" or similar display.
The latter display is seen, frequently, in an "Error 12" et al domain ownership verification demand.
And the domain root redirection, properly selected.
More essential details, for a custom domain published blog:
Third party domain settings
X Redirect nitecruzr.net to blogging.nitecruzr.net.
If you are requesting assistance with your custom domain published Blogger blog, the latter details, in both a screen print and text copy, will be useful.
And a zone editor display, for my domain "nitecruzr.co.uk".
A zone editor display, from GoDaddy. Every registrar will have a different display.
Comparing the URLs in the browser window, and in the Publishing window - and in Dig logs and zone editor displays (for custom domains) - we can identify typographical errors, and other mistakes. Typographical errors can be a cause of various problems, when publishing blogs to custom domains - and to "blogspot.com".
Some problems result from failure to copy and paste, properly. They can be as challenging to diagnose, as failure to observe registrar name server syntax.
Having verified the URLs, in some cases, you will continue with an affinity diagnosis, and with a differential diagnosis. This is all part of my simple 12 link test set.
You, the blog owner, may consider "duplicate" and "redundant" to be synonyms. When we research a blog problem, "duplicate" != "redundant". Many confusing problems have been solved, by comparing combinations of various above details - and by finding inequality, in one or more displays.
Diagnosing problems with #Blogger blogs can require careful diagnostics, using details found in dashboard screen prints and detail text copies, in Dig logs, and in HTTP traces. All details must be carefully compared, both visually and using text extracts, to diagnose some problems.
Much of this may seem superficial, to experienced support analysts - yet be obscure to some blog owners.