Contact support

We reply by e-mail, usually within two days.

Google reCAPTCHA checks this submission against abuse; data is sent to Google. The script loads only when this form is opened.

← All posts

Where a counter fits on a Blogspot blog

Blogspot continues to host many personal and community blogs, often with strict structural limitations. The platform confines custom HTML to designated sections, transforming the placement of an image counter into a critical design decision.

headerthe postsfootera narrow side column breaks first, and on a phone it lands next to the footer anyway

Where HTML is allowed at all

The layout editor is where custom markup is accepted, and it accepts it in one shape only: a box called a gadget, of which one variety takes raw HTML. The theme editor accepts more, but a mistake there affects every page at once, and undoing it is not always obvious.

A gadget is a named box that the theme positions for itself. It arrives with its own heading, its own margin and whatever width the surrounding section happens to have. Anything placed inside inherits all of that, which is why the same counter looks different in two sections of the same blog.

Why the side column is the wrong box

Inserting a counter within a narrow side column frequently causes layout disruptions. On mobile devices, sidebars are pushed to the very bottom, and a wide image design may exceed the available column width, leading to horizontal scrolling.

The side column is the narrowest section a Blogspot theme offers, and it is the first to be reflowed. A counter design wider than that column does not shrink to fit; it sticks out, and the page becomes scrollable sideways along its whole length, not only beside the image.

There is a second reason, and it is the one noticed too late. On a phone the side column is moved below the posts, which is exactly where the footer already is. The counter therefore ends up next to the footer regardless, having caused a layout problem on the way there.

Why the footer holds

The footer is consistently the most reliable location. It guarantees that the visual element loads only after the primary content is accessible, preventing any interference with the reading flow while accurately logging the visit.

The practical part is short enough to write without pictures. Add an HTML gadget, paste the tag into it, leave the gadget title empty so that no stray heading appears, drag it into the lowest section the layout offers, and save. Nothing else needs changing.

There are no screenshots here on purpose. The layout editor has been redrawn several times over the years, and a picture of last year's version is worse than no picture at all: it sends a reader looking for a button that has moved. The names have stayed put — layout, gadget, HTML — and names survive a redesign better than screenshots do.

The constraint turns out to be real but small. One box, one paste, and the placement question is settled for as long as the blog lasts. That is a fair trade on a platform that otherwise leaves very little to decide.

Advertisement