Before you send a pitch to any publication, there is a document you probably have not opened: its guest post guidelines. They tend to be brief, written plainly, and they decide whether your email gets a reply or a polite silence. This explainer covers what guest post guidelines are, what they typically contain, who applies them and how to read them in a few minutes, with no jargon and no tricks.
What are guest post guidelines?
They are the host site’s written conditions for outside contributors. Think of them as the house rules of a magazine that lets visitors write. They tell you the topics the editor wants, the format and length expected, how links and bios are handled, how long review takes and what gets an article refused.
Most sites publish them on a page called “Write for us”, “Contributor guidelines” or something similar. If you cannot find one, that is itself useful information, and a short question to the editor before you write anything is the sensible next move.
Why reading them first matters
An editor reads a large number of pitches. The fastest way to filter is to check whether the sender followed the instructions. A pitch that ignores the stated word range, the topic list or the submission method is declined in seconds, however well it is written. On the other side, a contributor who clearly read the page stands out, because that is surprisingly rare.
There is also a protective reason. Guidelines often say what will get your piece rejected or pulled after publication. Learning that before you write saves a rewrite and keeps your name clean with the editor.
What you will usually find inside
- Topic scope. Subjects the site covers and subjects it does not.
- Originality rules. Articles must be written for that site, not recycled from elsewhere.
- Link policy. How many links are acceptable and what they should point to.
- Format notes. Headings, length, tone, whether images are supplied.
- Process. Where to send a pitch, how long to wait, what happens after acceptance.
- Grounds for refusal. Promotional wording, thin content, unsupported claims.
Who enforces the rules?
Usually the editor or a small editorial team. They are the person who accepts, edits, schedules and, if needed, removes a piece. Find the name. If the page lists a contact for questions, use it before you draft, not after you are rejected.
A five-minute way to read them
- Skim the headings and spot the sections about topics, links and process.
- Copy the word range and any required format into your own notes.
- Underline every “do not”. These are the lines editors enforce hardest.
- Note the response time so you know when a follow-up is polite.
- Check whether the page has a date. Old guidelines may have been replaced.
How this connects to pitching well
Guidelines tell you what the host will accept. The pitch itself still has to be useful to that site’s readers. If you want a practical walk-through of that second part, our guide to pitching a focused article that editors accept picks up where this explainer stops, and the advice on building a repeatable outline for each submission helps you keep a pitch tidy once the rules are clear.
Common mistakes, in plain terms
People tend to repeat the same few errors. They send one pitch to many sites with a generic note. They exceed the length. They place links the policy does not allow. They assume a paid arrangement removes the need to follow the standards. None of these are cunning mistakes, only unread ones. Editors are not trying to catch you out; they are trying to protect their readers and their site, and the guidelines are how they say so.
It should go without saying that a rule page is not a puzzle to be gamed. Write something honest and useful, for a real audience, and respect what the host asks.
An example of the difference it makes
Imagine two contributors pitching the same editor on the same morning. The first has read the page, so the email names a topic from the site’s list, states the intended length inside the allowed range, and says the piece will be written for that site alone. The second sends a generic paragraph about “an article idea” with no detail. The editor does not need to be unkind to choose between them. The first email shows respect for the editor’s time, and respect is what a publication is really screening for.
The same gap appears after acceptance. The first contributor already knows how the byline works, how revisions are requested and when the piece will run, because it was all in the guidelines. The second spends a week on avoidable questions.
Rules beyond guest posting
The same thinking applies whenever you publish on a space someone else runs. Blogging communities, article sites and developer forums each carry their own norms. A directory like FreePostFinder, which gathers free publishing platforms to browse, has a guidelines note urging people to stay within the community rules that every listed platform sets for itself. That habit transfers neatly to guest posting: find the rule page, read it, then write.
What to keep in your own file
Create one simple record for each site you contact. Include the guideline page address, the date you read it, the word range, the link policy and the editor’s name. When you pitch again months later, check whether the page has changed before you reuse anything. Sites revise their conditions more often than most contributors notice, and a refreshed read takes two minutes.
Over time this file becomes a quiet advantage. You will notice that most hosts ask for roughly the same few things, such as original work, relevance and restraint with links, and that the exceptions are where you need to pay attention.
Quick answers
Do I really need to read them if I have written for similar sites?
Yes. Two sites in the same field can differ sharply on length, linking and tone.
What if the guidelines are vague?
Ask a short, specific question by email and keep the reply with your notes.
What if I disagree with a rule?
You may decline to write for that site. Pushing against a rule in a pitch rarely works.