Reader Zoom Level Affects Screen Space Needed

I have suggested that properly sizing the Jump Break and Title sections of each post is an important decision, when publishing a post in your blog.

Publishing this blog, using carefully sized post title and jump break sections, allows me to consistently publish posts, with maximum detail visible in main page view - and with the "Read more" link visible.

Potential readers may read a post in this blog - instead of returning to a SERP, and reading another blog. This affects a key reader retention metric, the "bounce rate".

All of that considered, sizing of the introductory post sections won't always produce predictable results.

Reader zoom level is a semi random factor, which makes blog section sizing less predictable than one would wish, when trying to increase reader retention.

I size my posts using "100%" zoom, in the Chrome browser. This may, or may not, produce the same effect, for readers using Edge / Internet Explorer, Firefox, or any other browser. And the differing browser will not be the only varying factor.

All of these details can affect zoom level, screen space requirements, and reader retention - for any different blog. Here it is helpful for the blog owner to know about the typical reader.

• Display screen size.
• Reader age.
• Multi tasking activity.
• Tech interest level.

Display screen size will affect how the blog sections look, to each reader.

Browser choice is not the only variation, that can affect screen space and blog section display sizes.

Reader display screen size used is a detail, that I cannot control. The computer on which I compose most posts has a 6" high screen. A second computer, that I use from time to time, has an 8" high screen. The second computer, even at a 125% zoom level, still displays more post content in one screen page.

This post (in main page view) displayed, at 100% zoom, on an 6" vertical display.



Let's compare this post, displayed at several zoom levels.

Here's this post, in the individual post page display - without Jump Break. See how it looks, zoomed in various font sizes. Note that here I use a maximised browser window, though some readers will resize the browser window to fit the blog content.

This post (in Preview mode) displayed, at 100% zoom, on an 6" vertical display.

This post (in Preview mode) displayed, at 100% zoom, on an 10" vertical display.

This post (in Preview mode) displayed, at 75% zoom level.



Smaller zoom is more likely to be used by people with better eyesight - using better resolution and more expensive computers, and smaller browser windows.

This post (in Preview mode) displayed, at 125% zoom level.



Larger zoom is more likely to be used by people with marginally worse eyesight. This will frequently involve older people.

Older readers will be more likely to use higher zoom levels.

Reader age is another detail which each blog author may consider, in blog design.

Blogs which attract older readers should be designed for displays which use higher zoom levels - or use larger fonts, to begin. Older readers, with marginal eyesight, will be more likely to surf the web with their browsers zoomed higher.

Multi tasking encourages smaller browser windows - and lower zoom levels.

Younger readers, who like to multi task, will probably use low zoom - and size the browser window smaller, so they can have multiple windows, simultaneously visible in large computer displays. Older readers will be more likely to focus on one task at a time - and will maximise the browser window, with higher zoom.

Blog subject may produce readers of differing age and tech interest.

Each blog, depending upon its content, may be more or less likely to interest readers of a given age and / or and tech interest level. People of different tech interest levels may also be more or less likely to use computers with higher resolution, and may multi task using smaller browser windows.

The bottom line.

Each blog owner will have to consider the various issues mentioned above - for each post published - and decide what screen sizes and zoom levels might be preferred by the target reader audience.

Only a blog owner can decide what reader audience may be more interested in each individual post - and may benefit from a specific zoom level. And this affects the proper sizing of the jump break and title section of each post.

---

Several details of a #Blogger blog audience affect what post title and jump break section will be more appropriate, for each individual blog. These details, in turn, can affect bounce rate / retention rate.

Verify BlogSpot And Domain URLs

Whenever dealing with any problem with a blog, you should verify the URLs involved.

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.

http://nitecruzr-test-ssl.blogspot.com

Here, we see the Blogger dashboard Settings - Basic page, for a "blogspot.com" published blog.

The Publishing display, for a "blogspot.com" published blog.



Useful text details, from Publishing, for a "blogspot.com" published blog:

nitecruzr-test-ssl.blogspot.com                                  Edit

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.

http://blogging.nitecruzr.net

Here, we see the Blogger dashboard Settings - Basic page. for a custom domain published blog.

The Publishing display, for a custom domain published blog.



Useful text details, for a custom domain published blog:

blogging.nitecruzr.net                                                  Edit
bloggerstatusforreal.blogspot.com                               redirects

With a custom domain published blog, next 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 domain root redirection, properly selected.



More essential details, for a custom domain published blog:

Third party domain settings
http://  blogging.nitecruzr.net
  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.

A zone editor display, for my domain "nitecruzr.co.uk".


A zone editor display, from GoDaddy. Every registrar will have a different display.


If you purchased the domain using a credit or debit account, the bank statement and / or charge advice will frequently have a description which details the purchase. In some cases, this will include the domain name.

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.

Buyer Beware - Don't Buy Pre Published Blogs

Don't develop a blog, that's simply designed to host AdSense ads - and avoid pre published blogs, in general.

Blogs and websites that are blatantly designed as ad hosts are classified as "MFA" ("Made For Ads") - and are never accepted as AdSense hosts. AdSense, and Blogger, want blogs with quality content - informative, interesting, and unique.

Legitimate and useful blogs start with content that is important to the blog owner.

Blogger, some time ago, explicitly prohibited sale of blogs.

Either Blogger will delete the blog as spam - or AdSense will classify it as "MFA".

If you buy a blog, "blogspot.com" or custom domain, with content already in place, it will probably contain copyrighted material. If Blogger does not delete / lock it as spam, AdSense will probably classify it as "MFA" - and the blog will never display ads.

Blogger blogs are based on personal interest. When you buy a pre published blog / domain, you're buying somebody else's discarded personal interest.

Most people who sell blogs do so after learning that what they have won't host ads or get traffic. Pre used blogs are frequently subject to disapproval, by AdSense - or DMCA / Spam classification, by Blogger.

If you do the research, you'll find out why the previous owner sold it to you.

You'll probably end up with a disabled AdSense or Blogger account - and doing the research, you'll find out why the previous owner sold it. It's like a "lemon law" car. If the price seems too good to be true, it probably is just that.

You would never, knowingly, buy pre worn underpants. Why would you buy a pre published blog? Start with an available URL, and add your own content. That's how you get content, reputation, and traffic.

---

#Blogger blogs are supposed to be based on personal experience or interest - using content that's informative, interesting, and unique. Purchasing a previously published blog, with content left in place, violates that principle.

A smart blog owner starts with an empty blog - using an available URL, and adds content.

Search Engine Reputation, And Vanity Domains

One hot Internet topic, these days, involves specialised ("vanity") domains.

The hot names seem to change, by the week. This week, enom is hyping ".family", ".live", ".rocks", and ".social". Other registrars may have other recommendations.

The blog Address (Name) is a key blog identity element, in a well designed blog. It's visible both to people, and to search engine crawlers.

The requirement that addresses must be unique is a supposed benefit of vanity top level domains - but vanity TLDs, alone, will not provide blog uniqueness. There will always be competition for some names, in any useful Top Level Domain.

My suspicion is that the shinier the TLD, the more competition you may see, between people who plan their uniqueness around choosing the perfect name.

Any popular blog / website subject will have name competition.

I could publish this blog as "chucksblog.com" - and that would be a shiny and unique name. Until another "Chuck" registered "chucksblog.us", or maybe "chucksblog.name". How unique would "chucksblog" be, then? How many readers could I expect, if they know "chucksblog" - but can't remember if it is "chucksblog.com", "chucksblog.info", or "chucksblog.name"?

If your blog has a popular subject, you won't have a unique name - unless you register your name, in every possible TLD that might be relevant to your name. And that will be a financial limitation, for many blog owners.

What name would you want your blog to have? For a truly shiny domain, you'll have competition.

Complete uniqueness == No competition == No interest == No readers.



McDonalds, for instance, may be able to register "mcdonalds.com", "mcdonalds.franchises", "mcdonalds.hamburgers", "mcdonalds.smallbusiness", etc (as each hypothetical TLD comes online) - and local domains "mcdonalds.co.uk", "mcdonalds.de", "mcdonalds.us", and so on.

Very few of the readers of this blog will be in a financial position to do all of that.

enom is hyping ".family", ".live", ".rocks", and ".social" - this week.



Your uniqueness strategy should include content.

You will have to develop a "uniqueness" strategy based on content - not solely on the address. You will need to understand that your blog may lose traffic, from people who know the blog "name" - but may not remember if "yourname" is a ".com", ".net", or ".us".

Of course, if you publish only to "blogspot", you will automatically have "yourname.blogspot.com", "yourname.blogspot.co.uk", "yourname.blogspot.de", and so on. You won't have "yourname.com", "yourname.net", and "yourname.us", however - unless you pay for the privilege.

Are you getting a feeling for the complexity of the branding issue? Good. Concentrate on content. The search engines index your blog - and provide you traffic - based on informative, interesting, and unique content.

Google denies the value of vanity domains, for raw SEO.

AdWeek weighs the issue, in What’s in a Name on Social?.

When it comes to vanity domains, Google has long denied that they affect search rankings. Their in-house tech team advised way back that registering a vanity domain for the sheer, hopeful sake of page rankings would be a fool’s errand. But there’s a solid number of marketers that disagree, and they watch these things very closely. Chalk it up to wishful thinking, if you like, but time will tell. And there are only so many .com domains available.

Only time will tell. I suggest that you keep your traffic and uniqueness strategy diverse. Don't depend upon a vanity domain, alone, for search reputation and traffic.

For best results, keep it in perspective.

Consider the name issue, if you want. But keep it in perspective. Blogger blogs will benefit from well written and unique content - as much as from a carefully chosen name / URL.

---

Some #Blogger blog owners are intent on publishing a blog to a custom domain, using a top level domain that relates to the blog subject. They do this, hoping to have a unique blog name.

They may overlook the idea that Blogger blogs benefit from well written and unique content, as much as from a shiny and unique URL.

Renaming Your Blog, And Historical Stats Pageview Counts

Occasionally, we see odd questions about Stats, and the history of someone's blog (or maybe, the URL of someone's blog), in Blogger Help Forum: Get Help with an Issue.

If I started my blog last year, why does my Stats display show pageviews from 2, or even 3, years ago?

and

If I rename my blog to a better URL, how do I carry the Stats numbers to the new URL?

Neither blog owner shows an accurate understanding of the historical nature of Stats pageview counts.

The Blogger servers record access activity by URL - not by blog.

Stats extracts pageview counts as needed, by URL, from the Blogger server logs. If the URL of your blog is "myfineblog.blogspot.com", and you request pageview counts for your blog, for "All time", you will see pageview counts against "myfineblog.blogspot.com", for Stats since May 2006 (as currently the case).

If the URL of your blog was "myexcellentblog.blogspot.com" until you renamed the blog to "myfineblog.blogspot.com" 6 months ago, you will see historical pageview counts for "myfineblog.blogspot.com" - which will include your blog, starting 6 months ago. You won't see pageview counts for "myexcellentblog.blogspot.com", from a year ago, because you'll be seeing historical pageview counts for "myfineblog.blogspot.com".

If someone else had a blog, published to "myfineblog.blogspot.com", before you renamed your blog to its current URL, your Stats displays could include pageview counts reflecting access to that blog. If "myfineblog.blogspot.com" was never used before you renamed your blog to that URL, it's possible that your pageview counts include attempted access to a non existent URL.

If you're using Google Webmaster Tools with your blog (and you should be doing that), you can check the access logs for "404 Not Found" events in the WMT logs. Just as a tree, falling in the forest, makes a sound even when nobody is around, so can access attempts exist against URLs where no blog is published.

Some referer spam appears to be sent to all likely URLs, ignoring whether or not a blog actually exists, at that URL. Referer spam is not unique to Blogger, and has been a problem since before Blogger became a major player in the Internet world.

If you just started a blog, or just renamed your blog to its current URL, your pageview counts can reflect historical referer spam, against your current URL, from before your blog was published to the current URL. As Blogger identifies specific referer spam campaigns, and eliminates some referer spam from Stats logs, this is one more possible cause of fluctuations in pageview counts.

If the possibility of seeing bogus pageview counts, for your blog as published to the current URL, does not please you, I will again point out that you'll get more out of your blog if you spend less time worrying about the details of the Stats displays, and more time working on your blog.

Look at activity before the blog was published as "noise", and look at current activity as "signal" - and work on improving the "signal to noise" ratio. Be aware of the value of your blog, and work on improving the value.

>> Top

What's The BlogID Of My Blog?

This blog is (for those of you not familiar with it) "The Real Blogger Status".

The URL (name) of this blog is currently "http://blogging.nitecruzr.net/", and it was previously "http://bloggerstatusforreal.blogspot.com/". Subject to the details involved in the renaming process, I am entitled to rename this blog anytime that I wish, and the name (URL) can change, anytime I do so.

There is another "name" for the blog, that does not change (unless I should perform a blog / URL swap).

The BlogID is the internal name, that's setup when the blog is first created. Look at the source for the blog, in the header.

<head>

...

<link href='http://blogging.nitecruzr.net/' rel='canonical'/>
<link rel="alternate" type="application/atom+xml"
title="The Real Blogger Status - Atom"
href="http://blogging.nitecruzr.net/feeds/posts/default" />
<link rel="alternate" type="application/rss+xml"
title="The Real Blogger Status - RSS"
href="http://blogging.nitecruzr.net/feeds/posts/default?alt=rss" />
<link rel="service.post" type="application/atom+xml"
title="The Real Blogger Status - Atom"
href="http://www.blogger.com/feeds/24069595/posts/default" />
<link rel="EditURI" type="application/rsd+xml" title="RSD"
href="http://www.blogger.com/rsd.g?blogID=24069595" />

There we see two places to find the BlogID.

If you are a blog member, you can also find the BlogID in a few links in your dashboard. In some cases when asking for help in Blogger Help Forum: Something Is Broken, you may need the BlogID, as well as the URL.

Since the BlogID is easily visible in the blog source code, you'll not hide it with any useful result. The BlogID, when known, won't provide a hacker or blog thief access to the dashboard. Any URL which contains "blogID" can only be used by a blog owner or administrator.

If I were unlucky, and this blog was to be locked as suspected spam, the BlogID would become the LockedBlogID. In this case, the LockedBlogID may be the only thing useful in Blogger Help Forum: Something Is Broken.

What's The BlogSpot URL Of My Blog?

We see this question a lot, in Blogger Help Forum: How Do I?

Hello! What's the address of my blog?

and generally it motivates a simple answer.

Can you view the blog online? If so, look in the browser address window.

or

Can you login to Blogger? Find the "View Blog" link.

There are cases when the above advice, though technically correct, doesn't help answer the original question.

• If the blog was deleted or locked as spam (righteously or unrighteously), it won't be online. The Asker of the question will be instructed to undergo the hated 4 step protocol.


• If the blog was published to a custom domain, the BlogSpot URL will be available in only one specific place. The Asker will be instructed to look at Settings - Publishing - "Advanced Settings" - "We won't leave your readers behind!"


• If the blog was deleted or locked, and it was published to a custom domain, only the lockedblogID will be available - and that will be only from the dashboard "Restore Blog" link.

>> Top

Your Blog Is Like You - Unique

The title of this blog is "The Real Blogger Status".

This blog contains many posts. The name of this blog is "bloggerstatusforreal", and its URL is now "blogging.nitecruzr.net" (it's also known as "bloggerstatusforreal.blogspot.com"). There can be only one BlogSpot blog with the name "bloggerstatusforreal", though there can also be "bloggerstatusforreal.com", and "bloggerstatusforreal.net", and each can be separate web sites, if desired. And any blog can have the title of "The Real Blogger Status".

You can create another blog, if you wish.

You can create as many blogs as you need, and they are all free. Use the Dashboard link "Create a Blog", to create another - but you will have to use another blog name - if you wish to publish to "BlogSpot.Com". If you want to create another blog in a custom domain cluster, that's easy enough, after you create a BlogSpot blog.