The naming problem starts before the pitch
Pitch anxiety usually gets diagnosed as a courage problem. It’s more often a naming problem. If a tour stop is called “Guest Post,” the pitch email has nothing to lead with — no hook, no promise, no reason for the host to care. The host reads the subject line, scans for relevance, and moves on. Experienced book bloggers say they can judge a pitch’s interest level within about three seconds of scanning it, according to Laura Fabiani’s guide for iRead Book Tours. Three seconds is exactly how long a stop named “Guest Post” deserves.
Here’s the reframe: the tour stop name, the pitch subject line, and the host’s promotional copy are one decision made three times. If you can’t state the reader benefit in five words, the pitch has nothing to stand on, and the host has nothing to post. Solve the naming problem before recruitment begins, and every downstream step gets easier.
Why “Guest Post” kills response rates
A generic stop name fails on both ends of the transaction. For the host, it signals copy-paste outreach — and hosts detect form letters reliably. Jennifer Mattern, who receives dozens to over a hundred guest post pitches weekly at All Freelance Writing, is blunt: “We really can tell if you just plugged our names and blog information into your form email.” For readers, “Guest Post” promises nothing. Chapter’s guide to organizing book blog tours ranks guest posts as a medium-engagement format, below reviews, exclusive excerpts, and interviews — and a nameless guest post is the weakest version of an already-middling format.
The relevance problem compounds this. In Cision’s State of the Media survey, only 7% of journalists said the majority of pitches they receive are relevant to their audience, and nearly three out of four told Muck Rack they reject pitches for irrelevance to their focus area. Book bloggers face the same inbox math. A stop name that doesn’t map to what the host’s audience already reads is a pitch that reads as irrelevant before the host finishes the subject line.
Name stops by the job they do
Every stop on a tour has a job: review, interview, craft essay, excerpt, giveaway. Chapter’s guide notes that variety across stops gives readers multiple reasons to check out the book — but variety of format isn’t enough. The name itself has to carry the reader benefit. Compare:
- “Guest Post” vs. “Why I Rewrote Chapter 4 Six Times” — the second promises a story a writer-reader will click.
- “Interview” vs. “Five Questions About Writing What You’d Rather Forget” — the second tells the host’s memoir audience exactly what they’ll get.
- “Excerpt” vs. “The Scene My Editor Almost Cut” — the second gives the host a promotional hook they can paste straight into their post.
Notice what these names have in common: they describe what the host’s audience receives, not what the author finds easiest to produce. That single shift is the whole method. The name becomes the pitch’s opening hook, the host’s promotional copy, and the reader’s reason to click — one artifact doing three jobs.
The subject line is the stop name under pressure
Once the stop has a real name, the pitch subject line mostly writes itself. Fabiani’s guide calls a catchy subject line a core hooking element, and notes some bloggers request specific wording — if a host’s review policy says to include “Book Review Request” in the subject line, follow it. The HuffPost guide on blogger outreach goes further, calling the subject line one of the most important pieces of a pitch: too long, vague, or boring, and it won’t get noticed, especially on phones.
A workable pattern: [Stop name] — [Book Title] ([Genre]), tour stop [date range]. The stop name carries the hook; the rest is logistics the host needs anyway. Keep the whole pitch under 200 words, personalize the first sentence with something specific from the host’s blog, and never bcc a batch. The payoff from personalization is documented: a marketer pitching 100 targeted bloggers one at a time, with individual touches, got 80 yeses for an unknown romance author with no platform. That result came from relevance and specificity, not from a bigger list.
Pressure-test every candidate name
Before committing a name to a pitch, run it against three questions about the host:
- Does it match their recent posts? Mattern lists pitching a topic the blog doesn’t cover — or one that already exists on the blog — among the top reasons pitches get ignored. Read the last month of posts before naming.
- Does it fit their review policy? Chapter’s guide recommends checking genre fit, activity level, audience, and review policy before pitching. A stop name that ignores stated sensitivities or format preferences is a fast no.
- Would their commenters click it? Look at what actually gets comments and shares on the host’s site, not just what they publish. If your candidate name doesn’t resemble anything their audience engages with, rename it.
If any answer is no, rename before sending. This costs maybe ten minutes per host — against the hours you’d spend writing content for a stop that never gets accepted.
Where a title generator fits (and where it doesn’t)
Generating candidate names for ten stops is genuinely draining, especially at the end of a work night when decision fatigue has already set in. A tool like the Unsloppy book title generator fits here as a pressure-testing aid: it’s for generating candidate stop titles and hook phrasing during the planning phase, so you have raw material to test against the three questions above. Budget roughly an hour to generate and shortlist names for a ten-stop tour — that’s a recommendation for time-boxing, not a measured savings figure.
When this isn’t worth it: if you have fewer than about five stops, or you already know each host’s audience well enough to name the stop directly, skip the generator entirely. A generator produces candidates; it doesn’t make decisions. The pressure test — host’s posts, host’s policy, host’s commenters — is still yours to run, and a shortlist you can hold in your head doesn’t need tooling.
A worked example (hypothetical, labeled as such)
Picture an author with a memoir and eight planned stops. The first draft of the tour plan reads: Guest Post, Interview, Excerpt, Review, Guest Post, Interview, Excerpt, Giveaway. Every pitch subject line would be some version of “Blog Tour Invitation — [Title].” Functional, and forgettable.
The renamed version: “The Memory I Got Wrong” (craft essay), “Five Questions About Writing What You’d Rather Forget” (interview), “The Scene My Editor Almost Cut” (excerpt), plus the review and giveaway stops, which keep their format names because those formats carry their own weight with readers. Each pitch subject line now opens with the stop name. Each host can lift the name straight into their promotional copy. The point of this example is the method — no response-rate lift is claimed, because none has been measured. What’s structurally true is that the renamed pitches give hosts a reason to reply and readers a reason to click that the format-only names never did.
Debrief: what to log after the tour
The naming system only compounds if you document it. In your tour spreadsheet — the same one tracking blog name, contact, pitch status, and confirmed date — add three columns: the subject line sent, whether the host replied, and the engagement on the published stop (comments, shares, referral traffic). After the tour, the pattern is usually visible: which names drew replies, which drew reader engagement, and which drew neither. That log, not a follower count, is what sharpens the next tour’s names. A tour that produces a documented naming record is a repeatable campaign asset; a tour that produces only a pile of sent emails is a launch-week party you’ll have to re-plan from scratch next time.
Start with the stops you’ve already drafted. If any of them is named after its format alone, that’s the first fix — and it costs an evening, not a publicist.