Diagnosing Geographical Location / IP Address

We see various problems reported, in Blogger Help Forum: Get Help with an Issue, which may involve geographical or network relationships.

Why can't I regain access to my blog, that I stopped publishing 5 years ago?

and

Why can't I see my blog?

and

Why does my dashboard show up in a language that I can't read?

With questions like these, it helps to know how and where the owner and / or readers of the blog get Internet service.

Geographical location and IP address are useful details, when diagnosing various problems with our blogs.

• Access and authentication.
• Connectivity.
• Language.

Address / location diagnosis is not a difficult procedure, given the right tools. As an example, click on each of these three links, one by one. Print or copy text details, as convenient - then combine and compare the details, from the different services.

• IP-Details.com : Find your IP address Information
• IP Location Finder - Geolocation
• Locate IP Address Lookup Show on Map

There are other similar tools, that I may identify later.

I'll show each location discovery tool, from various geographical locations. This will illustrate the uncertainties of geographical vs geolocated location - and why use of multiple ("redundant") online diagnostic tools is a good idea.

I clicked on each link, twice - while connected differently - and made the screen prints from these geographical locations. I may show additional locations as I use them.

• 22 May, 2016: MacDonalds, Martinez CA
• 23 May, 2016: StarBucks, Martinez CA

"IP-Details.com"
Date: 22 May, 2016
Diagnosed Location: Austin, TX
Geographical Location: MacDonalds, Martinez, CA
IP Address: 64.134.233.29
Provider: MacDonalds

"IP Location"
Date: 22 May, 2016
Diagnosed Location: Valencia, CA
Geographical Location: MacDonalds, Martinez, CA
IP Address: 64.134.233.29
Provider: MacDonalds

"Info Sniper"
Date: 22 May, 2016
Diagnosed Location: (Los Angeles, CA)
Geographical Location: MacDonalds, Martinez, CA
IP Address: 64.134.233.29
Provider: MacDonalds

"IP-Details.com"
Date: 22 May, 2016
Diagnosed Location: Bedminster, NJ
Geographical Location: MacDonalds, Martinez, CA
IP Address: 70.197.3.7
Provider: Verizon Cellular

"IP Location"
Date: 22 May, 2016
Diagnosed Location: Rohnert Park, CA
Geographical Location: MacDonalds, Martinez, CA
IP Address: 70.197.3.7
Provider: Verizon Cellular

"Info Sniper"
Date: 22 May, 2016
Diagnosed Location: (Los Angeles CA)
Geographical Location: MacDonalds, Martinez, CA
IP Address: 70.197.3.7
Provider: Verizon Cellular



---

"IP-Details.com"
Date: 23 May, 2016
Diagnosed Location:
Geographical Location: StarBucks, Martinez, CA
IP Address: 50.247.110.187
Provider: StarBucks

"IP Location"
Date: 23 May, 2016
Diagnosed Location: Menlo Park CA
Geographical Location: StarBucks, Martinez, CA
IP Address: 50.247.110.187
Provider: StarBucks

"Info Sniper"
Date: 23 May, 2016
Diagnosed Location: Milpitas CA
Geographical Location: StarBucks, Martinez, CA
IP Address: 50.247.110.187
Provider: StarBucks

"IP-Details.com"
Date: 23 May, 2016
Diagnosed Location: Bedminster, NJ
Geographical Location: StarBucks, Martinez, CA
IP Address: 70.197.12.193
Provider: Verizon Cellular

"IP Location"
Date: 23 May, 2016
Diagnosed Location: Salinas CA
Geographical Location: StarBucks, Martinez, CA
IP Address: 70.197.12.193
Provider: Verizon Cellular

"Info Sniper"
Date: 23 May, 2016
Diagnosed Location: South San Francisco CA
Geographical Location: StarBucks, Martinez, CA
IP Address: 70.197.12.193
Provider: Verizon Cellular

"IP-Details.com"
Date: 5 June, 2016
Diagnosed Location: Bedminster, NJ
Geographical Location: Martinez, CA
IP Address: 70.213.0.103
Provider: Verizon Cellular

"IP Location"
Date: 5 June, 2016
Diagnosed Location: Berkeley CA
Geographical Location: Martinez, CA
IP Address: 70.213.0.103
Provider: Verizon Cellular

"Info Sniper"
Date: 5 June, 2016
Diagnosed Location: Oakland CA
Geographical Location: Martinez, CA
IP Address: 70.213.0.103
Provider: Verizon Cellular



Geolocation is a useful diagnostic tool, when diagnosing various Blogger problems - but geolocated details, using the above tools (or complementary procedures), need to be persistently cross checked. Tomorrow, or from a different location or service, one may see different results.

Access and authentication.

Sometimes when trying to regain access to a dormant blog, you'll be advised to access from the previously used computer. Google uses location comparisons, as part of demographic authentication.

Connectivity.

Some blog disconnections may have geographical origin. Knowing where you, and other blog readers may be (or appear to be), can be useful in determining a geographical relationship between problems.

Language.

Blogger uses geolocation to determine appropriate local language. Knowing where you are - or appear to be - can be useful in determining why you may be seeing the Blogger dashboard and / or your blog, in a given language.

The bottom line.

Along with blog address / name / URL verification, location diagnosis is a useful procedure - but the results need to be considered discretely.

---

When diagnosing various access / connectivity problems with #Blogger, knowing the IP address and location of the reported problem is useful. It's easy to get the desired details - but the details may need to be verified, carefully.

https://productforums.google.com/d/topic/blogger/4LkxHxYsj1c/discussion

Read More

BlogLovin Has Problems With Some Blog Feeds

We see occasional reports, in Blogger Help Forum: Get Help with an Issue, from Blogger blog owners who want to share their blogs using BlogLovin.

Why can't I claim my blog?

BlogLovin is somewhat monolithic. They use the blog feed, and a BlogLovin URL with embedded token, to process / validate blog claims - and their diagnostics, when a claim is a problem, are not always effective.

Some blog feeds can be validated, yet not be found by BlogLovin. And other feeds won't validate.

Blog owners have reported several common problems, when trying to claim their blog with BlogLovin.

• Start with the published blog URL.
• Empty / very short feeds.
• Redirected feeds, generally involving FeedBurner.
• Feeds containing GeoRSS datapoints.
• Feeds with content formatted in Microsoft Office.
• Positioning the claim verification link / token.

Start with the published blog URL.

Even though BlogLovin uses the blog posts newsfeed for content source, when you claim your blog, you need to use the published URL. You do not specify the feed URL. BlogLovin finds the feed URL from the blog header - after you give it the published URL of the blog.

Feeds can be validated, using either the W3C Feed Validator, or the FeedValidator.org Feed Validator. You have to use the right W3C validator, though.

If the blog is published to a custom domain, the published URL - and the feed - will be most consistently accessible to BlogLovin when the domain is properly setup. Bogus DNS addressing, or poorly setup domains, will cause feed access issues - and BlogLovin won't process your claim.

Empty / very short feeds.

An empty or very short feed just does not contain enough material, for BlogLovin to reliably claim a blog.

It's best to let your blog mature slightly, before trying to use it with BlogLovin. Half a dozen good posts are better than just one or two, when claiming a blog.

Redirected feeds, generally involving FeedBurner.

A FeedBurner redirected feed looks completely different from a native Blogger feed. If you're going to use a Blogger blog in BlogLovin, it's best to use a non redirected version of the feed for your blog.

Feeds containing GeoRSS datapoints.

A feed from a blog that includes a GeoRSS datapoint will fail validation.

GeoRSS will disrupt BlogLovin, and cause problems with FeedBurner. If you want to use either service, you have to edit any post using GeoRSS, and remove the GeoLocation element.

Feeds with content formatted in Microsoft Office.

A Microsoft Office formatted blog will produce a validated feed - yet BlogLovin and FeedBurner will both have problems, when using the feed.

We've been dealing with Microsoft Office generated problems, in various Blogger features, for years. BlogLovin is one more service where Microsoft Office formatted posts just don't work.

Both the W3C and FeedValidator.org feed validators are generally used, to diagnose non claimable blogs.

But neither is 100% useful, when there's a problem. Some blogs with valid feeds still can't be claimed.





Use the right validator.

You do need to use the right W3C validator, when checking the feed for your blog. Some BlogLovin diagnostic instructions may mention the wrong validator.

W3C provides 2 validator services.

This is for HTML / XML Markup Validation:

http://validator.w3.org/

This is for Feed Validation:

https://validator.w3.org/feed/

If you use the Markup Validator, with a blog feed, you're going to see a lot of irrelevant errors. You have to use the Feed Validator.

Use a properly coded template.

Some blogs cannot be claimed, because BlogLovin cannot detect a feed. If your blog lacks the necessary header records in the template, your blog cannot be claimed.

This problem is not caused by BlogLovin. This is a problem caused by you, using a custom template that lacks the necessary template content.

BlogLovin does have a good Help contact page, though.



Positioning the claim verification link / token.

BlogLovin suggests publishing a new post, with the claim link / token at the top of the post - or alone. I found that the link, added to an HTML gadget, and positioned in the sidebar, works - and makes more sense than cluttering the blog posts newsfeed with a gratuitous post containing a claim link.

Proper positioning of the claim link - whether in a post or the sidebar - is also essential to the success of the claim process.

As last resort, contact BlogLovin Support for help.

If you just can't get your blog claimed, you can contact BlogLovin Support - or you can read the BlogLovin Help database.

---

Some #Blogger blog owners use BlogLovin as a social sharing platform. Unfortunately, not every blog owner can successfully claim their blog, in BlogLovin, immediately.

BlogLovin has several possible problems with Blogger blogs - and not all problems are well known.

Read More