Your Blogger post can be beautifully written and still sit outside Google like a suitcase left on the curb.
If Search Console says “Submitted URL marked ‘noindex’”, it means Google found a URL you submitted for indexing, but the page itself is telling Google not to index it. Today, in about 15 minutes, you can separate the harmless cases from the urgent ones, check Blogger’s robots settings, inspect the page source, clean up your sitemap, and request validation with much less guesswork. This guide gives you a practical repair path for Blogspot and custom-domain Blogger sites without turning your afternoon into a server-room opera.
What This Search Console Error Really Means
The error sounds dramatic, but the logic is plain: Google received a URL through a sitemap or another submitted source, then discovered a noindex instruction on that URL. It is a mixed message. Your sitemap says, “Please consider this page.” The page says, “Please leave me out.” Google obeys the page-level instruction.
On Blogger, this often happens after theme edits, custom robots header tag changes, label page experiments, or accidental indexing settings. I once saw a blogger spend three evenings rewriting titles when the actual culprit was one tiny checkbox under custom robots tags. The title was innocent. The checkbox was holding the tiny lantern in the fog.
This is not always bad. Some Blogger URLs should not be indexed, such as search result pages, certain archive pages, preview-like URLs, or thin label pages. The real job is to decide whether the affected URL is a valuable post, a static page, or a low-value system URL.
- Submitted means Google found the URL through a sitemap or submitted source.
- Noindex means the page tells Google not to include it in search results.
- The fix depends on whether the URL deserves to be indexed.
Apply in 60 seconds: Open the affected URL list in Search Console and mark each one as “valuable post,” “static page,” or “system/archive URL.”
Why Search Console Uses This Wording
Search Console is not saying the URL is broken. It is saying the URL is excluded from indexing because of a directive. That directive can come from a meta robots tag, an HTTP header, or platform-generated settings. In Blogger, the most common source is the custom robots header tags area.
Google’s own Search Central documentation explains that noindex is a directive for excluding pages from Google Search when Google can access and crawl the page. That last part matters. If you block crawling and also add noindex, Google may not be able to see the noindex instruction clearly. That combination is where many tidy plans grow horns.
The Practical Meaning for Traffic
If the affected URL is a core blog post, fixing it can restore the page’s chance to be indexed. If the URL is a label archive, search page, or low-value duplicate, the right move may be to leave it alone and remove it from submission sources where possible.
A tiny anecdote from the Blogger trenches: a craft blogger once asked why twelve recipe pages vanished from search. The problem was not recipe schema, image size, or her charming habit of naming every dessert “Grandma’s little cloud.” Her post pages inherited a noindex setting after a theme migration. One settings change brought the pages back into the indexing queue.
Who This Is For, and Who Should Not Panic
This guide is for Blogger and Blogspot site owners who see Submitted URL marked “noindex” in Google Search Console. It also helps if you use a custom domain on Blogger, because the same settings can apply behind the polished domain name.
It is especially useful for solo bloggers, niche site owners, small publishers, affiliate writers, local business bloggers, and anyone managing content without a developer on speed dial. If your blog is a little publishing kitchen with one cook, one timer, and too many browser tabs, you are in the right place.
This Is For You If
- You submitted a Blogger sitemap and now see noindex errors.
- Important posts are not appearing in Google Search.
- You recently changed Blogger custom robots settings.
- You installed or edited a custom Blogger theme.
- You are unsure whether label, archive, or search pages should be indexed.
- You want a calm checklist instead of panic-clicking every setting in the room.
This Is Not For You If
- You are using WordPress, Shopify, Wix, or a custom CMS with different indexing controls.
- You want to force Google to rank a page immediately. No setting can promise that.
- You are trying to index private, duplicate, empty, or low-quality pages.
- You are dealing with legal, medical, or financial compliance content that requires professional review before publication.
| URL Type | Likely Action | Why |
|---|---|---|
| Published blog post | Fix noindex | A real post usually belongs in search if it is useful and original. |
| Static page such as About or Contact | Usually fix | Brand and trust pages can support credibility. |
| Label page | Usually leave noindexed | Many label pages are thin or duplicate archive views. |
| Search results page | Leave noindexed | Internal search pages rarely help users from Google. |
| Archive page | Depends | Thin monthly archives can compete with posts. |
For deeper Blogger structure planning, your internal guide on Blogger category architecture pairs well with this article because indexation problems often start with category and label decisions.
The 5-Minute Diagnosis Before You Touch Settings
Before editing Blogger settings, inspect the affected URL. This saves time and prevents the classic “fixed the wrong door while the window was open” problem.
Open Google Search Console, go to Indexing, then Pages, then select the report for Submitted URL marked “noindex”. Export the list if there are many URLs. You are looking for patterns: Are they all posts? All labels? All mobile URLs? All pages from one month? Patterns are the footprints in the flour.
Diagnosis Step 1: Check the Exact URL Type
Blogger can produce several URL patterns. A normal post often looks like /2026/07/post-title.html. A static page often uses /p/page-title.html. Label pages often use /search/label/label-name. Search URLs and archives may look different again.
If only label or search pages appear, you may not have a real post-indexing problem. If regular post URLs appear, keep going. That is where the repair work matters.
Diagnosis Step 2: Use URL Inspection
Paste one affected URL into the URL Inspection tool. Look for clues such as:
- Indexing allowed? No: noindex detected
- User-declared canonical
- Google-selected canonical
- Crawled as smartphone
- Last crawl date
- Sitemap source
I like to test three URLs, not one. One URL can lie by accident; three URLs usually start singing in harmony. If all three are regular posts with noindex, your site-level or theme-level setting may be the source.
Diagnosis Step 3: View the Page Source
Open the affected URL in a browser. Right-click and choose View Page Source. Search for noindex. If you see something like <meta name="robots" content="noindex">, you have confirmation.
If you do not see noindex in the source, inspect the live URL in Search Console. Google may be reading a different version, a cached pattern, or a header-level directive. Blogger usually keeps the mystery small, but custom templates can add theatrical fog.
Visual Guide: The Blogger Noindex Repair Flow
Open the Search Console report and group URLs by post, page, label, archive, or search type.
Use URL Inspection and page source to confirm where noindex appears.
Fix valuable posts and pages. Leave thin system URLs out of the index.
Adjust Blogger robots header tags, theme code, sitemap submission, or canonical signals.
Request indexing for important URLs and validate the fix after live inspection passes.
Where Blogger Can Add Noindex Without You Noticing
Blogger has indexing controls in settings that can affect your homepage, posts, pages, archives, and search pages. These controls are useful, but they are also small enough to be changed casually and forgotten, like a house key tucked into the wrong coat.
The main place to check is Settings, then Crawlers and indexing. You may see options for custom robots.txt and custom robots header tags. The labels can feel simple, but the consequences are not tiny.
Custom Robots Header Tags
In Blogger, custom robots header tags may include options such as all, noindex, nofollow, none, noarchive, nosnippet, noodp, notranslate, noimageindex, and unavailable_after. You do not need most of these for normal publishing.
For most Blogger sites, published posts and pages should not have noindex selected. Archive and search pages may be noindexed depending on your strategy. If your posts are marked noindex, that is the SEO equivalent of writing a letter and sealing it inside a drawer.
Homepage Tags
Your homepage should usually be indexable. If the homepage is noindexed, Google may still discover internal URLs, but your brand entry point becomes weaker. For a niche blog, the homepage is often the front desk, map, and first handshake.
Post and Page Tags
This is the big one. If posts and pages are set to noindex, your core content can be excluded. Turn off noindex for posts and pages you want in search. Then test a live URL.
Archive and Search Page Tags
Many Blogger owners intentionally noindex archive and search pages. That can be fine. Thin archive pages often repeat snippets from posts and do not offer much unique value. Your internal guide on preventing thin archive pages from being indexed is a natural companion here.
- Posts and static pages should usually be indexable.
- Label, search, and thin archive pages may be intentionally noindexed.
- Always test a live URL after changing settings.
Apply in 60 seconds: Open Blogger settings and check whether noindex is selected for posts and pages.
Sitemap Problems That Trigger the Error
The word submitted matters. It means Google found the URL through a submitted sitemap or another explicit discovery path. If your sitemap includes URLs that are noindexed on purpose, Search Console may report the conflict.
Blogger automatically provides sitemap feeds, but site owners often submit multiple versions. Some submit /sitemap.xml, feed URLs, atom feeds, RSS URLs, and older variations. That can create a cluttered signal set. Not disastrous, but untidy. Google can handle mess; it just does not send thank-you cards for it.
Common Blogger Sitemap URLs
Typical Blogger sitemap paths may include:
- https://example.com/sitemap.xml
- https://example.blogspot.com/sitemap.xml
- Feed-based URLs used by older guides
For a custom domain Blogger site, submit the sitemap under the preferred canonical domain. If your live site is on HTTPS at your custom domain, do not keep relying on old blogspot-domain sitemap submissions unless you have a specific reason.
What to Remove From Search Console
Removing a sitemap from Search Console does not remove pages from Google. It simply stops that sitemap from being used as a submitted source. If a sitemap is outdated, duplicated, or pointing to URLs you no longer want indexed, remove it and submit the cleaner version.
A tiny field note: one publisher had four submitted sitemaps, two from an old Blogspot address and two from the custom domain. Search Console looked like a kitchen drawer full of chargers. Cleaning the submitted sitemap list did not rank pages overnight, but it made diagnostics much easier.
Sitemap Troubleshooting Table
| Search Console Clue | Likely Cause | Best Next Step |
|---|---|---|
| Submitted URL marked noindex | URL is in a submitted sitemap but carries noindex | Remove noindex for valuable pages or stop submitting low-value URLs. |
| Alternate page with proper canonical | Google sees another URL as the preferred version | Check canonical and internal links. |
| Discovered, currently not indexed | Google knows the URL but has not indexed it yet | Improve quality, internal links, and crawl signals. |
| Crawled, currently not indexed | Google crawled but did not index | Assess content uniqueness and search value. |
For a deeper sitemap repair process, see your internal article on Blogger sitemap troubleshooting. It fits neatly beside this noindex fix because sitemaps are often the messenger, not the villain.
Robots.txt vs Noindex: The Tiny Difference That Causes Big Confusion
Robots.txt and noindex are often mentioned together, but they do different jobs. Robots.txt controls crawling. Noindex controls indexing. In plain language: robots.txt can tell bots not to enter a room; noindex tells Google not to put the room in its public catalog.
For Blogger owners, this distinction matters because a custom robots.txt mistake can hide a page from crawling, while a noindex directive can keep a crawled page out of results. They are cousins, not twins.
What Robots.txt Does
Robots.txt gives crawl instructions. If you disallow a path, Google may not crawl that path. But if Google finds links to a blocked URL elsewhere, it may still know the URL exists. Blocking a URL does not always remove it cleanly from search results.
What Noindex Does
Noindex tells Google not to show that page in search results. For noindex to work reliably, Google needs to crawl the page and see the directive. This is why blocking a page in robots.txt while also adding noindex can create a weird little tug-of-war.
Simple Rule for Blogger
For pages you want indexed, do not block them in robots.txt and do not apply noindex. For pages you do not want indexed, noindex is often more direct, provided Google can crawl the page. For private pages, Blogger is not a secure access-control system; do not publish sensitive material and rely on robots settings as a lock.
Show me the nerdy details
A page can be excluded from Google Search by a meta robots noindex tag in the HTML source or by an X-Robots-Tag HTTP header. Blogger users usually encounter the HTML meta version because Blogger settings and templates generate page markup. Robots.txt uses path-based crawl rules, such as Disallow lines. If a URL is blocked from crawling, Google may be unable to refresh or confirm the noindex directive on the page. For troubleshooting, inspect the live URL, check the rendered HTML source, and avoid using robots.txt as a substitute for page-level index controls.
If you have customized robots.txt before, review your internal guide on Blogger custom robots.txt before changing anything else. Robots files are small, but a misplaced slash can wear a villain cape.
Which Blogger Page Types Should Stay Noindexed?
Not every noindex report is a problem. Some noindex signals are good housekeeping. The goal is not “index everything.” The goal is to index the pages that deserve search visibility and keep thin, duplicate, or utility pages out of the way.
Think of your blog as a small bookstore. You want readers to find the books, not the broom closet, receipt drawer, or every shelf label printed as a separate pamphlet.
Post Pages
Most original posts should be indexable. If a post is thin, outdated, duplicated, or intentionally private, you may decide otherwise. But a useful article with original value should not carry noindex.
Static Pages
About, Contact, Privacy Policy, and disclosure pages can be indexable. They may not bring huge search traffic, but they support trust. For sites that review products, discuss money, or publish advice, trust pages matter. The FTC often emphasizes clear disclosures in advertising and endorsements, and readers also appreciate knowing who is speaking.
Label Pages
Blogger label pages can be useful for readers but weak for Google if they only list snippets of posts. If you use labels as serious category hubs with custom intro text, clean internal links, and strong topical grouping, they may deserve more attention. If they are thin archives, noindex is usually sensible.
Your article on noindex tag pages on Blogger is especially relevant here because label and tag-style pages are frequent guests in this error report.
Archive Pages
Monthly archive pages are often low-value for search. Readers usually want the best answer, not every post from April arranged like a pantry inventory. Archive pages can help navigation, but indexation is optional.
Internal Search Pages
Internal search pages should generally stay out of Google’s index. They can create infinite combinations, weak result pages, and duplicate paths. Let them help users inside the site, not compete with your own posts in search.
| Question | Score 0 | Score 1 | Score 2 |
|---|---|---|---|
| Does the page answer a distinct search intent? | No | Partly | Clearly |
| Is the content original? | Mostly duplicate | Mixed | Strongly original |
| Would a search visitor be satisfied? | Unlikely | Maybe | Yes |
| Does it support trust or navigation? | No | Somewhat | Strongly |
Decision cue: A score of 6 to 8 usually deserves indexation. A score of 0 to 3 usually does not. A score of 4 or 5 needs editorial judgment, which is a polite way of saying: pour coffee, look at the page honestly, and do not let vanity drive the bus.
Step-by-Step Fix for Blogger Posts and Pages
Now we move from diagnosis to repair. The fix is usually simple, but the order matters. Do not start by requesting indexing. First remove the noindex signal, then test the live page, then request indexing or validate the issue.
Step 1: Confirm the URL Should Be Indexed
Ask one question: would this page be useful if someone landed on it from Google? If yes, proceed. If no, leave the noindex in place and consider whether it should be removed from submitted sitemaps or internal index-priority links.
Step 2: Check Blogger Visibility
In Blogger, go to Settings. Confirm the blog is visible to search engines. If search visibility is turned off, your site is sending the wrong invitation to Google. It is the digital equivalent of hosting a dinner party with the porch light off.
Step 3: Review Custom Robots Header Tags
Still in Blogger settings, open Crawlers and indexing. If custom robots header tags are enabled, inspect homepage, archive and search pages, and post and page settings. Remove noindex from post and page settings if you want posts and pages indexed.
Step 4: Inspect the Theme
Go to Theme, then edit HTML only if you are comfortable. Search for noindex. Some custom themes include conditional meta robots tags. If the theme adds noindex to item pages, posts may be excluded even when Blogger settings look fine.
Before editing theme code, back up the theme. This is not cowardice; this is adult supervision in zip-file form.
Step 5: Test the Live URL
Return to Search Console. Use URL Inspection, then Test Live URL. If Google no longer detects noindex, request indexing for important URLs. For many affected URLs, use validation on the Pages report.
Step 6: Wait for Recrawl
Search Console reports are not instant. A fixed URL may take days or longer to move out of the error report. The live inspection result is often a better immediate signal than the report dashboard.
- Do not request indexing while noindex is still present.
- Back up your Blogger theme before editing HTML.
- Use live inspection to confirm the repair.
Apply in 60 seconds: Pick one valuable affected post, test it live, and confirm whether noindex is still detected.
Mini Calculator: Indexation Priority Score
Use this tiny calculator to decide which affected URLs to repair first. Keep the numbers honest. The calculator is not magic; it is a lantern.
Priority score: Enter values and calculate.
Short Story: The Recipe Post That Wore an Invisible Cloak
A food blogger once wrote a careful post about weeknight lentil soup. It had photos, substitutions, storage tips, and the kind of intro that smelled faintly of garlic and winter rain. But Search Console kept showing the page as submitted and noindexed. She rewrote the title. She shortened the intro. She changed the slug. Nothing moved.
Then we inspected the live URL. There it was: a noindex tag quietly sitting in the source code, added by a template condition meant for archive pages but accidentally applied to item pages. One misplaced condition had put the whole post in an invisible cloak. After backing up the theme, fixing the condition, and testing the live URL, the noindex warning disappeared from inspection. The lesson is plain: when Search Console gives a technical clue, read the page’s instructions before rewriting the page’s soul.
Technical Checks for Themes, Canonicals, and Redirects
If Blogger settings look correct but the error remains, check technical signals. This is where custom themes, canonical tags, mobile templates, redirects, and old domains can muddy the water.
Most Blogger users do not need advanced technical work. But if your site uses a heavily customized template, third-party scripts, old mobile parameters, or a custom domain migration, the issue may not live in the obvious settings panel.
Check Canonical Tags
A canonical tag tells search engines which version of a page is preferred when duplicate or similar URLs exist. A canonical tag does not replace noindex. If a page has both canonical and noindex signals, Google must interpret a mixed set of instructions.
For Blogger custom domains, check whether the canonical points to the correct HTTPS custom domain version. If your internal links point to one version and canonical tags point to another, indexing diagnostics become muddy.
Your internal guide on fixing duplicate canonical URLs on Blogger is a useful next read if the URL Inspection tool shows unexpected canonical choices.
Check Redirects
If an affected URL redirects to another URL, inspect the final destination. Sometimes Search Console reports a submitted URL, but the noindex exists on the target page. Use the final live URL as your truth source.
Check Theme Conditions
Blogger templates can use conditional logic. A custom theme might noindex archive pages, search pages, or error pages. That is normal. The problem begins when the condition accidentally includes post pages.
Search your theme for these strings:
- noindex
- robots
- data:blog.pageType
- data:view.isPost
- data:view.isPage
- data:view.isArchive
- data:view.isSearch
If that looks like a spellbook, do not edit blindly. Back up the theme and consider help. One missing bracket can turn a neat repair into a confetti cannon.
Check Mobile and Parameter URLs
Older Blogger setups may create mobile URLs with ?m=1. Google usually handles mobile-first indexing, but parameter versions can still appear in diagnostics. Inspect the canonical relationship between desktop and mobile parameter URLs.
Decision Card: When the Theme Is the Suspect
Decision Card: Theme-Level Noindex
Suspect the theme if:
- Blogger settings look correct, but page source still shows noindex.
- The issue started after a theme change.
- Only one template type is affected, such as posts or static pages.
- Multiple posts share the same noindex pattern.
Best action: Back up the theme, search for robots directives, and test one edited copy before changing your live publishing workflow.
Common Mistakes That Keep the Error Alive
The most stubborn noindex errors usually survive because the fix is applied in the wrong place or checked too soon. Search Console is a dashboard, not a microwave. Some things need recrawling.
Mistake 1: Requesting Indexing Before Removing Noindex
Requesting indexing does not override noindex. It only asks Google to crawl or recrawl the URL. If the page still says noindex, Google will keep excluding it.
Mistake 2: Fixing Label Pages That Should Stay Noindexed
Some site owners see any error and treat it as a fire. But label pages may be intentionally noindexed. The better question is: should this URL be in search at all?
Mistake 3: Submitting Too Many Sitemap Variations
Multiple outdated sitemap submissions can make reports harder to read. Keep the clean sitemap for the preferred domain and remove stale submissions from Search Console. Again, this does not delete URLs from Google; it cleans the diagnostic signal.
Mistake 4: Blocking Crawling and Expecting Noindex to Be Seen
If robots.txt blocks Google from crawling a URL, Google may not see the current noindex or index signals on the page. Avoid using robots.txt and noindex in a messy pile unless you know exactly why.
Mistake 5: Editing the Theme Without a Backup
Always back up your Blogger theme before editing HTML. The ten seconds you spend exporting the theme can save an evening of trying to remember what the code looked like before the gremlin sneezed.
Mistake 6: Confusing “Indexed” With “Ranking”
Fixing noindex only makes a page eligible for indexing. It does not guarantee ranking. After the technical fix, the page still needs useful content, internal links, crawlable structure, strong titles, and a clear reason to exist.
- Do not chase label-page warnings blindly.
- Do not expect indexing requests to override noindex.
- Do not edit Blogger theme code without a backup.
Apply in 60 seconds: Write down the exact URL type before changing any setting.
When to Seek Help
This topic is not medical, legal, financial, insurance, tax, cyber-risk, or physical safety advice. Still, SEO settings can affect business visibility, lead flow, and publishing revenue. Treat major changes carefully, especially on sites that support income.
Seek technical help if your site has hundreds of affected valuable URLs, a heavily customized theme, a recent domain migration, complex redirects, or mixed canonical signals. If your Blogger site supports client acquisition or affiliate revenue, an hour of competent review can be cheaper than a week of anxious experiments.
Quote-Prep List for an SEO or Blogger Developer
If you hire help, prepare these items before asking for a quote:
- Your Blogger admin access level, without sharing passwords in plain text.
- Search Console property type: domain property or URL-prefix property.
- Export of affected URLs from the noindex report.
- Three example URLs that should be indexed.
- One example URL that should stay noindexed.
- Recent changes: theme edits, custom domain setup, sitemap submissions, robots.txt edits.
- Your preferred canonical domain, including HTTPS and www or non-www.
| Help Type | Typical Scope | Budget Cue |
|---|---|---|
| DIY checklist | Settings review, live inspection, sitemap cleanup | Free, but requires care |
| SEO audit mini-session | Report review and prioritized fixes | Often lower-cost than a full audit |
| Blogger theme repair | Template code review and robots tag correction | Cost rises with customization |
| Full technical SEO audit | Indexing, canonicals, internal links, content quality, schema | Best for revenue sites or large archives |
For broader Search Console repair habits, your internal article on Google Search Console troubleshooting can help turn one-off fixes into a repeatable maintenance routine.
FAQ
What does “Submitted URL marked noindex” mean in Google Search Console?
It means Google found the URL through a submitted source, often a sitemap, but the page contains a noindex directive. Google is therefore excluding the page from search results. The fix is to remove noindex if the page should be indexed, or stop worrying if the URL is intentionally excluded.
How do I fix “Submitted URL marked noindex” on Blogger?
First confirm the affected URL is a valuable post or page. Then check Blogger Settings, especially Crawlers and indexing and custom robots header tags. Remove noindex from posts and pages that should appear in Google. After that, use Search Console’s URL Inspection tool to test the live URL and request indexing.
Should Blogger label pages be noindexed?
Often, yes. Blogger label pages can be thin archive-style pages that repeat post snippets. If your label pages are not carefully built as useful category hubs, noindex can be a sensible choice. If they have unique text, helpful organization, and strong internal links, you may evaluate them differently.
Why does Search Console still show the error after I fixed Blogger settings?
Search Console reports can lag behind live changes. Use URL Inspection and test the live URL. If the live test no longer detects noindex, the repair is probably working, but the report may need time to refresh after Google recrawls the page.
Can robots.txt cause a submitted URL marked noindex error?
Robots.txt does not create noindex by itself. It controls crawling. However, robots.txt can make troubleshooting harder if it blocks Google from crawling a page where you changed index settings. For pages you want indexed, avoid blocking them in robots.txt.
Is noindex bad for SEO?
Noindex is not automatically bad. It is useful when applied to pages that should not appear in search, such as thin internal search pages or low-value archives. It is bad when accidentally applied to useful posts, important pages, or revenue-driving content.
How long does it take Google to reindex a fixed Blogger post?
Timing varies. A live inspection can confirm the fix quickly, but full report updates and indexing changes may take days or longer. Strong internal links, useful content, clean sitemap signals, and a request for indexing can help Google reassess the URL.
Can I ignore this error if only archive pages are affected?
Usually, yes, if the archive pages are intentionally noindexed and do not need search visibility. Still, review the list to make sure important posts or pages are not mixed into the report. The danger is not the report itself; it is missing valuable URLs inside it.
Does fixing noindex guarantee higher rankings?
No. Removing noindex only makes the page eligible to be indexed. Rankings still depend on content quality, relevance, internal links, technical accessibility, competition, user satisfaction, and Google’s evaluation of the page.
Conclusion: Turn the Signal Back On
The mystery from the opening is now less mysterious: your Blogger page was not necessarily broken, weak, or ignored. It may have been sending Google a simple instruction to stay away from the index.
Your next 15-minute move is straightforward. Open Search Console, choose three affected URLs, classify them by type, inspect one valuable post live, and check whether Blogger or your theme is adding noindex. If the URL should be indexed, remove the directive, test the live page, then request indexing.
Keep the pages that deserve search visibility open to Google. Keep thin system pages quietly out of the index. That balance is not glamorous, but it is the kind of technical housekeeping that lets good writing be found instead of standing in the hallway with its coat on.
Last reviewed: 2026-07
