How this article was produced: it was written with AI assistance, working alongside the site owner during the same sessions in which the problems happened. The owner directed the work and checked the results on the live site. The measurements come from Lighthouse and Google PageSpeed Insights runs on the live pages, and scores vary slightly from run to run.
This blog runs on Blogger. We wanted a faster, cleaner theme (our mobile PageSpeed Performance score was 70 and the Largest Contentful Paint was 5.7 seconds) and a contact form that actually emails us new leads. Neither job went smoothly. Below is the honest list of what broke.
Results first: what changed
| Mobile Lighthouse measurement | Before | After |
|---|---|---|
| Performance score | 70 | 97 to 100 (mobile 97-99 across runs, desktop 100) |
| Largest Contentful Paint | 5.7 s | 2.0 s (mobile) |
| Cumulative Layout Shift | 0.149 | 0 |
| Home page HTML size | about 186 KB | about 41 KB |
The gains came mostly from removing three web-font files, dropping leftover widgets, and giving every image a fixed shape. The theme itself has no external CSS or fonts.
Error 1: "Please select an xml or text file"
What we saw: uploading the theme through Theme, Restore showed this message and nothing happened.
Why: the upload was sent without a recognised file type, so Blogger's check refused it.
Fix: choose the file with the browser's own file picker so the .xml file type is attached. Do not rename the file to .txt, which leads to the next error.
Error 2: the live site showed raw template code
What we saw: after a retry, visitors saw literal text such as <data:blog.pageTitle/> instead of a page. Blogger's theme page now called the template "Classic".
Why: a plain-text upload is stored as a first-generation Classic template, which does not process the modern layout tags.
Fix: restore the original theme backup through the native file picker. This is why you should always download a backup first (Theme, the arrow next to Customize, Backup) and test the restore path before you need it.
Error 3: the theme loaded but the posts area was empty
What we saw: header and footer rendered, the main area was blank, and the Layout page showed an empty section with no "Add a Gadget" link.
Why: two causes. Our new theme named its main section differently from the old one, and Blogger had kept the existing Blog Posts gadget attached to the old name. We had also set the section to showaddelement='no', which hides the add button.
Fix: give the new main section the same id as the previous theme used, and set showaddelement='yes' until everything works.
<b:section class='main' id='main' showaddelement='yes'>
Error 4: post summaries were blank on the home page
What we saw: every card showed a title but no summary text.
Why: the shortcut tag we used for the snippet returned nothing in this setup.
Fix: build the snippet from the post body explicitly.
<b:eval expr="snippet(data:post.body, {length: 170, links: false, linebreaks: false, ellipsis: true})"/>
Error 5: the author name was empty
What we saw: "By" with nothing after it, and an HTML comment reading "Substitution is not a singleton for tag [post.author]".
Why: the author is an object, not plain text.
Fix: use the name property, and make sure the display name on your Blogger profile is the name you want readers to see.
<data:post.author.name/>
Error 6: old gadgets kept appearing and broke accessibility
What we saw: PageSpeed reported an image without alt text, a link without a name and a malformed profile list, all from elements that were not in our theme.
Why: the previous theme's Featured Post, Popular Posts, Profile, Archive and Labels gadgets were still attached to the section we reused. One of them (Popular Posts) carried a cond attribute, so a simple search for its widget tag missed it.
Fix: in Theme, Edit HTML, remove the unwanted widget blocks, searching by widget id rather than by the exact opening tag. Keep gadgets you rely on, such as ad and tag-manager blocks.
Error 7: Edit HTML saved only on the second click
What we saw: changes pasted into the theme editor were lost, and the browser warned about unsaved changes when leaving.
Fix: after the first click on Save, wait for the "Processing" message, then click again if the page still reports unsaved changes. Always reload the editor and confirm the text is still there before assuming it saved.
Error 8: importing content created suffixed URLs and broke links
What we saw: imported posts got addresses ending in _3, _5 and so on, and the old addresses returned "page not found". Deleting the old pages also removed pages we had just edited, so footer links pointed at nothing.
Why: Blogger will not reuse a URL while the original item exists, and a deleted address stays unavailable to new items.
Fix: repoint the footer and menu links to the new page addresses, then add permanent redirects for every old post address under Settings, Errors and redirects, Custom redirects. In that dialog the From and To boxes already show a leading slash, so type the path without one. We verified each redirect returned a 301 status.
Error 9: the contact form said "sent" but nothing arrived
What we saw: a green "message sent" notice, an empty inbox and an empty spreadsheet.
Why, in three layers:
- The form's code showed success whenever the browser request finished, even when the script returned an error.
- The web app was still running version 1 of the Google Apps Script. Saving the script does not update a deployment; you must choose Deploy, Manage deployments, edit, New version.
- The destination sheet kept its old column headings, so new fields landed under the wrong titles.
How we diagnosed it: we posted deliberately invalid input (a blank name and a bad email) to the script address. The old version answered "success" to anything; the new version answered "invalid input". That one test tells you instantly which code is live.
Fix: deploy a new version at the same address, make the form show success only when the script says so, and rewrite the header row to match the new columns. We then sent labelled test messages and checked both the inbox and the sheet.
What we would do differently
- Download a theme backup and practise restoring it before changing anything.
- Reuse the existing section ids from the old theme.
- Test every form with invalid data first, so you learn which version is running.
- Check the live page source, not just the editor, after every save.
Sources and tools
- Chrome for Developers: Lighthouse overview (the tool behind the scores quoted above)
- Google PageSpeed Insights (the public tool we ran on the live pages)
- Blogger Help: Layout data tags (the template tags referred to in errors 4 and 5)
Summary
None of these errors was exotic. Each came from an assumption about how Blogger stores themes, widgets, URLs or script deployments. If you hit one of them, the fix is usually one setting or one line. If you are stuck on another Blogger problem, tell us through the contact page and we will add it to this log.
About the author: Junaid Sabir writes about practical AI and automation for people without a technical background. This article was drafted with AI assistance, then checked and edited by the author; the "What we have and have not verified" notes say which parts were tested.