Skip to content

Guest posts

Guest posts come in two kinds: those a guest writes on your website (incoming) and those you write on someone else’s website, with a link to a page of yours (outgoing, the guest posts proper). The ERP manages both: incoming ones go through the editorial plan like any piece, and for outgoing ones it watches the query they target and whether their link to your website is still there. It is in Marketing → Search visibility, Guests tab.

What is it for?

What does each article say?

ColumnWhat it is
ArticleIts title. Below it, its address once it is published
DirectionIncoming (they write on your website) or Outgoing (you write on another website)
Other websiteThe domain of the website where an outgoing one is published, or where the author of an incoming one comes from
SearchThe Google query an outgoing one targets, or the main query of an incoming one
AuthorWhoever writes it: a CRM contact
DateThe day it went out or, if it hasn’t gone out, the expected one
StatusProposed, accepted, published, rejected or withdrawn
Clash or warningFor an incoming one, its conflict with what is published and planned. For an outgoing one, whether it targets a query that already belongs to a page or piece of yours
LinkFor a published outgoing one, what the latest check of its link said: live, lost, changed to nofollow or could not be read

At the top, the filters by direction and by status, and the search box (title, domain, query, author or notes). If any published article has its link lost, changed to nofollow or pointing to another page, a warning in red counts them.

How do I add one?

In the bar at the top choose Incoming or Outgoing, type the title, the website (the domain, such as ‘blog.example.com’; pasting a whole address is fine) and the query, and click Add. Its record opens for you to complete the rest:

Click Save: everything is saved at once.

What happens with an incoming one?

When you register it, its piece in the editorial plan is created, of type Incoming guest post, with its author, its date and its main query. It is a piece like the others: you see it in the editorial plan and in the calendar, its conflicts are checked when it is created and every night, and on the guest post’s record you have Its piece in the editorial plan to go to it. What you change on the guest post’s record (title, author, date, notes, query, planned address and WordPress ID) also changes its piece, in the same save.

Accepting it requires it to pass the filter. When you click OK, the ERP checks its conflicts again and looks at the calendar warnings for its day:

If marketing decides to accept it anyway, type the reason in the record’s field and click OK: the conflict is accepted and the warnings skipped with that reason, which is what someone will read in a year’s time.

Rejecting it discards its piece and frees its query. Propose again recovers it, but the query doesn’t come back by itself: give it to it again on the record. Both things are done at the same time on the guest post and on its piece: either both change or neither does.

It is published by itself. When the synchronisation finds its page on your website (by the planned address or the draft ID of its piece, like any piece), it links it, the piece changes to published and so does the guest post, with the page’s address and its publication day. Put the planned address (or the WordPress draft ID) on its record so that it finds it without any doubt.

What happens with an outgoing one?

The query it targets is recorded as its own (it is its owner, just like a page or a piece). If that query is already the main query of a page or a piece of yours, it isn’t taken away from it: the article targets it as a secondary one and the ERP warns you:

‘free verifactu’ is already the main query of the page /verifactu-gratis/: an article on a domain with more authority may take its position. Better another angle or another query, or make the link point to that page.

If the linked page of yours is precisely the owner of that query, there is no warning: the article passes authority to it, which is what you want.

In addition, the pieces in your editorial plan that target that same query will see it in their conflict: ‘is already the main query of the guest post ‘…’ on another website’.

When it goes out, type the article’s address and the day, and click Published. From that moment its link is checked. If it is removed from the other website, No longer on the website marks it as withdrawn: its query becomes free and its link stops being checked. Rejecting it also frees its query.

Every week, if you turn on the example schedule ‘Comprobar los enlaces de los artículos invitados cada semana’ (it starts paused, like the others: see the publishing board), or whenever you want with Check links. The check runs in a separate process (you see it in System → Background jobs): while you have the tab open, the list updates by itself when it finishes.

The ERP reads the page of each published outgoing article and looks in it for a link to your website:

LinkWhen
LiveThe link to your page is still there. If it still goes to your website but to another page, it is too, and the record says where it now points
LostThe page no longer links to your website, or the article’s page no longer exists. If the page exists, the warning reminds you that a link drawn with JavaScript can’t be seen: open it and check it by hand before claiming it
Changed to nofollowIt was a normal link and now has ‘nofollow’, ‘sponsored’ or ‘ugc’: it no longer passes authority. One that was already nofollow or sponsored doesn’t count as a change
Could not be readThe other website didn’t respond, gave an error or responded with an anti-bot’s waiting page

An anti-bot isn’t a lost link. If the other website has an anti-bot (Cloudflare, Imunify360, Sucuri…) that doesn’t let the ERP through, its waiting page doesn’t have your link, but that doesn’t mean it has been removed: the ERP recognises it and leaves it as Could not be read, with the name of the anti-bot.

A link that is lost or changes to nofollow warns with the event ‘The link of a guest article on another website has been lost or no longer passes authority’, and the example schedule ‘Avisar de un enlace perdido’ leaves you a task in the module’s inbox, linked to the article. It warns once: if the following week it is still lost, it doesn’t warn again; if it comes back and is lost again, it does.

Where else do they appear?

Can I ask the assistant to do it?

Yes. ‘Which guest posts do we have published on other websites’, ‘has any guest post link been lost’ or ‘on which other people’s blogs do we have a link to our website’ read the articles with the status of their links. ‘Check whether the links of our guest posts are still there’ queues the check; like every assistant action, it shows it to you before doing it. To register or change them, use the tab.

What permissions are needed?

To see guest posts, View on Search visibility. To add, change, accept, reject, publish, withdraw and check links, Changes.

What doesn’t the guest post check do?

Back to search visibility.

More about Search positioning