When you publish a guest article, the name above it carries your site's credibility. If that name belongs to nobody, or to somebody other than the person described, you pay for it in reader trust. Checking who a contributor is lies with the publisher, not the contributor, and it can be done without asking anyone for a passport.
Short answer: Use public evidence: a profile that matches the author's own claims, a consistency check between bio and profile, and a light two-step test that the author controls the profile. Do not collect ID documents as a routine step. If an author cannot be verified, you can decline, publish under an editorial byline with permission, or show only what you verified. If you run a blog or magazine that accepts outside writers, these steps fit into your acceptance flow.
What you are actually trying to establish
Verification has a narrow goal: reasonable public evidence that the person writing to you is the person described in the bio. It does not aim at proving legal identity, and it does not judge the writing, which is the editor's separate task. Keep the goal narrow and the check light, and you can apply it to every contributor without making honest writers feel interrogated.
Google's helpful content page frames why authorship matters. It asks whether it is self-evident to visitors who authored the content, whether pages carry a byline where one might be expected, and whether bylines lead to further information about the authors. It strongly encourages accurate authorship information and says any form of deception makes a page untrustworthy to both users and automated quality systems. Source: Google Search Central: Creating helpful, reliable, people-first content (Opens in a new tab).
The page does not describe how to verify an author, so the method below is a practical suggestion for your own acceptance flow, not a Google requirement.
Where verification ends
- It ends at reasonable public evidence. Proof of legal identity is a different task with different data duties.
- It is done once and recorded, then revisited when the author's details change.
- It informs the editor's reading of the draft but does not replace it.
The three-way match: bio, profile and draft
A bio makes claims: a role, an employer, years of experience, places published. The profile the author supplies either supports those claims or contradicts them. The draft then shows whether the depth of knowledge fits. Matching all three is more telling than any single check.
| Check | How | Strong sign | Weak sign |
|---|---|---|---|
| Professional profile | Open the supplied address and compare name and title | Name, title and employer match the bio | New, empty or different from the bio |
| Prior publications | Search the name on independent outlets | Several sites, same field | Only pages that carry a link |
| Employer | Does the organization's site list the person? | A staff or author page names them | Employer does not know the person |
| Photo | Ask where the image comes from | The image appears only on the author's own profiles | Same image under different names on other sites |
| Email domain | If an organization is claimed, check the sender domain | Domain of that organization | Free mailbox with a corporate claim |
No row decides by itself. A writer with a thin profile may still be real, and a polished profile may belong to someone else. Read the rows together and ask the author to explain any mismatch.
Three questions to put in the record
- Does the name on the form match the name on the profile?
- Do the title and experience in the bio match what the profile shows?
- Does the depth of the draft fit the claimed expertise?
Patterns that deserve a second look
A fabricated profile can show several small flaws at once. None of the following proves anything; each is a reason to ask a question.
- A profile photo that may be a stock image or someone else's picture. Run an image search for its source.
- A very broad title that cannot be checked, such as "digital strategist" or "content expert".
- A profile created very recently with no history.
- An email name that does not match the author's name.
- Large claims with nothing measurable, such as "internationally recognized".
- The same bio sentences appearing word for word under other authors.
Do not try to decide technically whether a photo was generated. Ask for the source of the image and whether the author has access to it, which is a more reliable question. Three or more patterns together justify asking for extra evidence.
A two-step verification for the author
Two light steps show that the profile belongs to the person writing to you, without asking for any document.
Step one: link the email to the profile
Ask the author to message you through the profile itself, referring to the pitch, or to place a short agreed phrase in the profile and remove it afterwards. The first method is gentler and enough to start with. The aim is to see that whoever controls the profile is the person in your inbox.
Step two: a short new sample or conversation
Ask for two or three sentences of fresh opinion on the topic that were not part of the draft, or offer a short call. This is not an exam. It checks that the person who wrote the pitch also wrote the draft and that the expertise is real. A real specialist can meet that request easily, and a refusal is information too.
Decision question: should you ask for an identity document?
Practical suggestion: not as a routine step. An ID document is personal data, and storing, protecting and deleting it becomes your responsibility. Public evidence plus the two steps gives reasonable assurance for ordinary submissions. If your field makes legal identity critical, decide that together with your privacy policy and whoever handles data protection for you. What each situation requires is outside this topic; the suggestion here is only that public evidence comes first and documents remain the exception.
| Approach | Gain | Cost | Suggestion |
|---|---|---|---|
| Public evidence only | No data burden, fast | Limited assurance | Starting point for routine pitches |
| Public evidence plus two steps | Stronger match | Small extra effort for the author | Pitches with a link or an expertise claim |
| Identity document | Strong assurance | Personal data risk and author resistance | Exception, decided with data protection in mind |
Matching depth to risk
Not every guest post deserves the same effort. Calibrate to the claim, the topic and the link requested.
| Situation | Risk | Suggested check |
|---|---|---|
| General information piece, no expertise claim, no bio link | Low | Profile address and consistency |
| A professional title is asserted | Medium | Profile, organization page and photo |
| Commercial bio link, expertise claim and a consequential topic | High | Three-way match, two steps and a depth check in the draft |
| Topic that can affect a reader's health, legal or money decisions | High | All of the above plus independent evidence of the claimed field |
The table orders your effort; it is not a legal classification. When a topic can influence a reader's decisions, it is prudent to ask for independent support for the expertise claim.
When to repeat verification
- The author changes title, employer or field.
- The profile address changes or stops loading.
- The author proposes a topic far from the area you verified.
- A complaint or correction request arrives about an earlier piece.
If the author cannot be verified
A failed verification does not force a rejection. Four options exist, and the right one depends on the piece and the intent.
- Decline: the cleanest answer when the details conflict and no further evidence arrives.
- Publish under an editorial byline, with the author's explicit permission, when the content is valuable and the author prefers not to be identified. The author is not presented under a misleading identity.
- Show only what was verified: a name and a confirmed profile, and leave out unverified titles and expertise claims.
- Hold: if the author promises more evidence, keep the piece as a draft for a stated period.
In every case, keep unverified information out of the author box. Readers assume every line there was checked, and printing a title you did not verify helps present a false identity.
Building the author box and markup correctly
After verification, the author information should appear consistently on the page and in structured data. Google's Article documentation asks that every author presented on the page also be included in the markup, with separate entries for multiple authors, the Person type for people and the Organization type for organizations. The author name property should hold only the name: no publisher name, job title, honorific or introductory words such as "posted by". The documentation strongly recommends the url or sameAs property pointing to a page that uniquely identifies the author. Source: Google Search Central: Article structured data (Opens in a new tab).
For the page that collects a verified author's details, see how to build an author page for E-E-A-T. For how author information works in a writing service, see author information and E-E-A-T in article writing services. A written guest post policy page can state the rule in one sentence, for example that every guest author supplies a public profile address which you check before publication.
What the author box should contain
- The author name and a verified profile link.
- A verified title or experience in two or three sentences.
- An organization name only where the organization confirms the author.
- A short note on how the author relates to the topic.
Talking to the author about verification
Present verification as routine, not as suspicion. A message such as "We check a public profile for every guest author. Thanks for sharing yours; could you send a short note through it?" tells the author the step applies to everyone. If an author objects, do not argue. Point to the policy, list the options and let the author choose.
A worked example: a woodworking blog
Example scenario: A woodworking blog receives a draft on dovetail joints from a writer who describes himself as a furniture maker and asks for a bio link to his workshop. He supplies a professional profile and several photos of his work.
The editor opens the profile. The name and title match the bio, and earlier posts describe workshop projects. A reverse image search shows the author photo only on his own profiles. He sends a short note through the profile, referring to the pitch. The draft contains specific details about wood movement and tool setup that fit the claim. The editor records "profile consistent, both steps done" and does not ask for a document.
Another contributor on the same blog describes himself as an award-winning designer, but his profile is new, his photo appears on two other recently created pages under different names, and he does not answer the verification request. The editor declines with an identity-not-verified code and keeps the record so a later pitch from the same profile is recognised.
Agency and organization submissions
Some pitches come from an agency or a company rather than one person. Then two people matter: the sender and the author whose name will appear. You do not need the same check for both, but you do need to record both, along with who actually wrote the draft.
- If an agency names a client as author, ask for written confirmation from that person that they approve the piece.
- If the byline will be an organization, mark it with the Organization type and link its home page.
- If several people wrote the piece, name each one separately instead of combining them in a single line.
- If the sender's identity and the author's identity blur together, show only the verified person in the author box.
One risk with organizational pitches is a real author who did not write the draft. The second step of the verification catches it: ask the author for a short new view on the topic, and see whether the person can speak about the draft. If they cannot, question the authorship claim.
What the reader sees
Verification also shapes the author box. For a verified writer, produce a short, concrete and checkable bio, and leave out any title you did not verify. A reader looking at the box should be able to answer three questions: who is this, why do they speak on this topic and where can I learn more about them?
Every statement in an author box is a claim your site stands behind. Draft the bio sentences with the author, get their approval and update the box if the profile changes after publication. Keep one title per author across articles; two different titles for the same person create needless doubt for readers and editors.
Roles and timing inside the team
In a one-person publication, the person who verifies is also the person who approves, so write the verification note before approving the draft. In a larger team, the intake owner or a separate editor can verify, and the result should travel to the editor reading the draft, who needs to compare the claimed experience with the depth of the text.
A verifier who sees something doubtful need not decide alone. A second editor's short view makes a rejection fairer and easier to defend. Write only observed facts in the note: "Profile is new, the photo appears under a different name on another site, no reply to the verification request." Leave out guesses about intent.
A time limit
Give verification an upper time limit. If an author promises more evidence, allow a reasonable wait, then close the pitch with an identity-not-verified code. Pitches that wait indefinitely leave the author in limbo and occupy space on the editorial calendar.
A verified author is a lasting asset
Once an author is verified, working together again is easier. If your archive holds a verified-author entry, later pitches need only a check of what changed: title, employer, profile address. That saves editor time and shows the writer you treat them as a trusted partner. For regular contributors, a dedicated author page collects the verified details in one place, and each article's author box links to it, which also matches the url or sameAs recommendation in Google's Article documentation.
What to keep in the record
Keep the smallest set that shows the check was done: profile address, date, the person who checked, which matches were made and the outcome. Do not store photo copies, private messages or personal details gathered from the profile beyond what the decision needs. The record lets you decide later whether to repeat the check when details change or a new piece arrives.
Mistakes in the verification itself
| Mistake | Result | Fix |
|---|---|---|
| Searching only the name, not the supplied profile | Matching the wrong person with the same name | Open the address the author gave you |
| Relying on follower counts | Counts are easy to inflate | Look at content and publication history |
| Judging a photo by eye | False certainty | Ask for the source and the author's access |
| Verifying by phone and not recording it | The reasoning disappears | Write a one-line note |
| Printing an unverified title anyway | Readers get unchecked claims | Print only what you verified |
| Asking everyone for an ID document | Needless personal data and lost pitches | Start with public evidence |
Three verification outcomes and what each changes
Verification looks like a yes-or-no question, yet the record is easier to use with three outcomes. Practical suggestion: write one of them next to every author.
| Outcome | Evidence | Effect on the published page |
|---|---|---|
| Verified | The profile matches the email and a new sample or call took place | Full bio and profile link |
| Partly verified | The profile matches but the job title or experience could not be confirmed | Publish only what you confirmed and leave the title out |
| Not verified | No profile, a mismatch, or no reply | Do not publish, or turn the piece into an editorial article that claims nothing about the author |
The trap in the middle row is printing the title anyway because the author declared it. Google's helpful content page says deception makes a page untrustworthy, and an unconfirmed title moves that risk onto your own page.
A scenario: the profile disappears after acceptance
A pottery supply blog accepts a glazing-safety article and verifies the author's profile. Two days before the planned date, the account is deleted and the email goes unanswered. A workable order of steps:
- Change the record to partly verified and note the date the profile closed.
- Remove the author name and link from the draft until the record is clear; a bare name is still an identity claim.
- If the article stands on its own sources, move the date to the next calendar slot and give the author a written deadline of three working days.
- If no answer arrives, do not publish and change the record to not verified.
None of these steps judges the writing itself. They only keep the byline from claiming something you can no longer show.
The short message to send while you wait
Make the message say three things: the article passed editorial review, the profile must be confirmed again before publication, and the deadline. For example: "Your article is accepted. Your profile link no longer opens; please send a current profile address or propose a time for a short call before we publish. We expect your reply within three working days." Keep the tone free of blame, since a closed account is not proof of bad intent.
Save the message in the record. When the deadline passes you do not owe the author a second reminder, because the first message already stated the deadline and the consequence.
Frequently Asked Questions
Do I need to ask a guest author for ID?
Not as a routine step. Practical suggestion: public evidence and a two-step check are a reasonable start; an ID document is personal data you would have to store and protect.
Does Google say how to verify an author?
No. The helpful content page asks whether authorship is self-evident and whether bylines lead to more information about the author; it does not prescribe a verification method.
How can I tell if a profile photo is fake?
Rather than judging the image technically, ask for its source, run an image search and check whether the same picture appears under other names.
Can I put a job title in the author name field?
Google's Article documentation says the author name property should contain only the name; titles and honorifics go in their own properties.
What if the piece is good but the author cannot be verified?
You can publish under an editorial byline with the author's permission, show only verified facts, or hold the piece while the author provides more evidence.
Do I repeat verification for every article?
No. Verify once and record it; check again when the author's title, employer or profile changes.
Conclusion
Verifying a guest author is how a publisher stands behind every name on its site. A public profile, a consistent bio, a source check on photos and titles and a two-step test of profile control give reasonable assurance without collecting identity documents. For authors you cannot verify, you can decline, publish under an editorial byline with permission, show only verified facts or hold the piece briefly. Keep unverified titles out of the author box either way.
If you want placements where the author details are clear and recorded, see our guest post service.
Post a comment
Please log in to leave a comment. Login