A publisher site is technically healthy enough to host a paid link when its post pages answer with stable success codes, missing pages answer with a proper 4xx code, and the address you were given either stays put or redirects once to its final home. Repeated 5xx errors, soft 404s and long or script-based redirects are reasons to hold or reject. The check needs a browser and its developer tools, and it suits site owners, online sellers and agencies who buy links or sponsored posts.
This is a short health probe, not a performance test or a security audit. It asks only whether the addresses behave consistently enough that a link placed there can be expected to stay reachable.
Why server behaviour changes what a link is worth
A link has value only while the page that holds it can be fetched and kept in the index. If the page errors out, Google cannot crawl it. If the address keeps moving through redirects, your link sits on a page whose real location nobody has pinned down. Technical health does not raise the value of a link, but it decides whether the value can survive.
Health, indexability and quality are three checks
Indexability asks whether noindex, a canonical or robots.txt keeps the page out of the index. Health asks whether the page answers reliably. Content quality and neighbouring links are separate again. Read together, the checks give a consistent picture of the site.
Where the facts come from
The status code facts below come from Google's documentation on HTTP status codes, network and DNS errors (Opens in a new tab) and its page on redirects and Google Search (Opens in a new tab). For a general reference on codes, see the HTTP status codes SEO guide. The question here is narrower: how a buyer judges a seller's site before ordering.
Probe one: server errors and crawl rate
5xx codes signal a server-side failure. Google's documentation says 5xx and 429 server errors prompt its crawlers to temporarily slow down crawling. For 500, 502 and 503, the crawl rate drops in proportion to the number of individual URLs returning errors, and after the server returns 2xx again the crawl rate rises gradually.
What happens to indexed pages
The documentation says URLs that were already indexed are kept for a time but are eventually dropped, and URLs that persistently return a server error are removed from the index. For a buyer, the consequence is direct: if the post that holds your link keeps failing, the page can leave the index and your link disappears from view with it.
How to see it by hand
Open the seller's post pages on different days and at different hours. In the network tab of the developer tools, read the status of the main request. If you see 500, 502, 503 or 429, record the date and time. A single error can be temporary. The same error on separate days is a pattern.
When the evidence is enough
The same page failing on two separate days, or several different posts failing repeatedly, is enough for hold or reject. To tell whether the whole site or only one section is affected, try at least three different posts.
Probe two: missing pages
How a site answers for a page that no longer exists says a lot about its upkeep. The documentation states that all 4xx codes except 429 are handled the same way: the content is treated as nonexistent, previously indexed URLs are removed from the index, newly encountered 404 pages are not processed and crawl frequency gradually decreases.
404 and 410 side by side
Because the documentation treats 4xx codes other than 429 identically, a buyer has no reason to prefer one over the other. What matters is that missing pages answer with a genuine 4xx code.
The soft 404 problem
The documentation describes a 2xx page that is empty or shows an error message as a soft 404 in Search Console. Open a made-up path on the seller's domain, for example a string of random letters. If the page says "not found" but the network tab shows 200, you have found one. The article on soft 404 errors, how to find and fix them goes deeper.
401 and 403 are not crawl limiters
The documentation says not to use 401 or 403 to limit crawling. A post page that returns one of them is closed to general access, so a link there may be out of reach for ordinary visitors. Ask the seller why.
A quick practical test
Open a few old post addresses from the archive. A removed post should answer with a 4xx code and a live post with 200. Removed posts that all redirect to the home page, or that keep returning 200, show weak handling of missing pages.
Probe three: redirect type and chains
A redirect sends a request for one address to another. If the address you were given redirects, you need to know where your link will end up.
Permanent versus temporary
According to the documentation, 301 and 308 are strong signals that the target should be processed, while 302, 303 and 307 are weak signals, with 307 equivalent to 302 and 308 to 301. The redirects page adds that permanent redirects show the new target in search results, while temporary ones keep the source page in results. Googlebot follows both, but only permanent redirects signal that the target should be canonical.
How many hops
The status code documentation says Google's crawlers follow up to 10 redirect hops by default. The redirects page gives no figure for chain length. For a buyer, seeing more than one hop is a reason to question how the seller manages addresses. Details on chains and loops are in the guide to fixing redirect chains and loops.
Ways of redirecting
The redirects documentation recommends a permanent server-side redirect whenever possible. It treats an instant meta refresh as permanent and a delayed one as temporary. For JavaScript redirects it says to use them only when server-side or meta refresh redirects are not possible, because rendering may fail and Google might never see the redirect. An address that redirects through script is therefore a warning sign.
Pin down the final address
If the address you were given permanently redirects elsewhere, ask for your link to be placed at the final address. The order note then matches the real URL, and a later change to the redirect will not leave you guessing.
Probe four: the address in the order itself
The last probe checks the single address that will carry your link. Everything above helps you judge the site, but the order is about one URL.
Confirm the exact address
Write down the full address, including protocol, domain, path and any parameters. Open it and read the status code and any redirect steps. If the address in the order differs from the address that finally answers 200, correct the order note.
Check it twice
Check the final address on two different days. If it answers 200 both times with no redirect, record it as the stable address. If it changes, ask the seller to explain before you pay.
What a single probe cannot prove
The probe shows the site as it behaved when you tested it. You have no access to Google's own crawl records, which the site owner can view in Search Console. Google's figures and wording can change, so check the current pages before relying on them. The probe promises no ranking outcome. It makes visible technical risks before an order is placed.
The probes in one table
| Signal | What it can indicate | How to see it by hand | Suggested outcome |
|---|---|---|---|
| 5xx repeating on different days | Unstable server, risk of dropping from the index | Status code in the network tab | Reject |
| 429 responses | Overloaded server | Status code in the network tab | Hold |
| A made-up address returns 200 | Soft 404 problem | Open a random path | Hold |
| Removed posts all redirect to the home page | Weak handling of missing pages | Open old post addresses | Hold |
| Long redirect chain | Unclear final address | Count steps in the network tab | Hold |
| Script-based redirect | Redirect may go unseen | Look for redirect code in the source | Hold |
| Steady 200 and correct 4xx behaviour | Healthy site | Probe on several days | Pass |
Decision rule: manual probing or a named tool
The open question is whether to recommend a tool for the check or to teach manual probing in the browser. Practical suggestion: teach the manual probe and name no tools. The coverage, price and availability of tools change, and the documentation names none. A manual probe works on any site, and its result can be kept as a dated screenshot.
The rule in five lines
- Persistent 5xx on separate days: reject.
- Soft 404 or poor handling of missing pages: ask the seller to explain, then hold.
- Long chain or script redirect: get the final address confirmed in writing, then hold.
- Stable status codes over several days: this check passes.
- Record date, code and a screenshot with the order note.
Checklist before you order
- Was the candidate post opened on different days, with codes recorded?
- Were three different posts tried?
- Was a made-up address opened and its code read?
- Were a few old post addresses opened?
- Does the address you were given redirect, in how many steps and with which codes?
- Is the redirect server-side or script-based?
- Are all findings, with dates and screenshots, attached to the order note?
Example scenario: an online language school
Example scenario: A language school that sells courses online is offered a sponsored article on an education blog. The school's marketer opens three posts on two consecutive days. One post loads on the first day and returns 503 on the second, while the home page answers 200 on both. She records the time, retries at a different hour and sees 503 again. The pattern points to an unstable server in the post section, and the outcome is reject.
On a second blog, a made-up path shows a "page not found" message while the network tab reports 200. She records a soft 404 problem and asks the seller in writing. The seller fixes the template, and the next day the made-up path answers 404. She notes the correction, passes the blog on this probe and moves on to the remaining checks.
A sample log entry
A log entry should be short and dated. For example: "Site X, post address Y. Probe on two days, three posts. Status 200 on all except one post returning 503 on the second day at the same hour. Made-up path returned 404. No redirect. Decision: hold, ask seller about the 503 and repeat in two days." Each line can be checked later, and the entry shows exactly what was seen.
Keeping the entry factual
Facts survive disagreement. A line such as "site seemed unreliable" gives a seller room to dispute it, while "503 on the second day at the same hour" does not. Keep the interpretation in the decision line and the observation in the evidence lines.
Seller objections and answers
When you report findings, sellers may reply with stock answers. Each objection has a concrete reply.
"Our server just slows down sometimes, that is normal"
Slowing down and returning an error are different things. Google's documentation says 5xx and 429 responses make its crawlers slow down temporarily, and that URLs which persistently return a server error are removed from the index. Your reply: you are talking about 5xx status codes, not sluggishness. Share the dates and times, and ask whether it was maintenance or a temporary load.
"We redirect removed posts to the home page, which is better"
Redirecting every removed post to the home page hides the missing page but does not replace a correct 4xx code. The documentation describes empty or error-showing 2xx pages as soft 404s, and the type and relevance of a redirect target matter as well. Your reply: ask which posts go to which address and whether the redirect is permanent.
"We redirect with JavaScript, that is fine"
The redirects documentation says to use JavaScript redirects only if server-side or meta refresh redirects are not possible, because rendering may fail and Google might never see the redirect. Your reply: ask for a server-side redirect, or for an address that needs no redirect at all.
Once the seller answers
If the seller fixes the issue, repeat the probe on a different day and log the result. If the seller declines, the decision becomes hold or reject depending on how serious the finding is.
Questions for the seller
Some information only the seller has. Ask in writing.
- Has the post section had outages or maintenance recently?
- How do removed posts answer: 404, 410 or a redirect?
- If the post address changes after publication, will you move the link to the new address?
- Were the site's addresses restructured before, and are the redirects still in place?
Interpreting replies
A concrete reply names a date and a method. "Everything is fine" settles nothing. If the seller mentions a migration or maintenance window, ask when it happened and repeat the probe afterwards.
When the probe cannot give a clear answer
Bot shields and access walls
Some sites apply protection against automated or heavy requests, and a page that opens in your browser may behave differently for another client. Record this as missing information, not as a fault. The documentation advises against using 401 or 403 to limit crawling, so ask the seller why a post page returns them.
Network and DNS failures
The Google status code page does not cover network or DNS errors, so no claim about them can be drawn from it. If you cannot reach the site at all, record that and tell the seller.
Short outages
A single 503 can come from maintenance or a short load peak. The documentation says that once the server returns 2xx again, the crawl rate rises gradually, so a short problem need not leave a lasting mark. Base the decision on a repeating pattern, not on one error.
How the probe fits with the other checks
The health probe is one step of the pre-screen and decides nothing alone. Indexability, neighbouring links and site history are separate checks. A site can be healthy and still block indexing, and the opposite also happens.
Order of checks
Practical suggestion: indexing and server health first, then neighbouring links, then history and finally the seller's terms. The first two are the cheapest and the most conclusive, and a reject there saves the time the later checks would take.
A single record per order
Gather every check in a single order record, so that the decision on a site sits in one place and the reason for each stage can be traced.
Probing again after launch
The site changes over time, so monitor the page that holds your link.
What to test a second time
The status code of the page, whether its address changed and any redirects. A page that begins returning 4xx has made your link unreachable. If it returns 5xx, probe over several days to tell a short outage from a lasting one.
When the picture changes
If the page was removed or moved, contact the seller in writing. If the terms are in the order note, they support a correction request. If a permanent redirect now sends the page elsewhere, confirm that the link is present at the new address.
How often to repeat
The documentation sets no interval. Practical suggestion: probe soon after publication, tie later probes to your reporting cycle and add each date to the log.
Mistakes at a glance
| Mistake | What goes wrong and what to do |
|---|---|
| Probing only the home page | The home page may be stable while the post section is not. Probe the post pages. |
| Deciding on one try | A single error may be temporary. Repeat on other days and at other hours. |
| Missing the soft 404 | A page that shows an error message while returning 200 looks fine on screen. Read the code in the network tab. |
| Judging redirects by eye | The browser applies redirects silently. Count the steps and read their codes in the network tab. |
When you probe for a client
Health probing is one of the first steps in a pre-screen. A shared record lets the team re-evaluate a returning site quickly.
Log fields
Site name, probe dates and times, the addresses tried, status codes, the made-up path result, redirect steps and the decision.
Tracking drift
Technical status moves from day to day, and one probe never shows a site's normal state. Practical suggestion: probe on at least two separate days, and repeat the probe before any new order.
What the client sees
For a rejected site, write the finding plainly: "Post pages returned 503 on two separate days." The client sees that the decision rests on observation.
Frequently Asked Questions
How do 5xx errors affect Google's crawling?
Google's documentation says 5xx and 429 responses make its crawlers slow down temporarily. URLs that persistently return server errors are eventually removed from the index.
Is there a difference between 404 and 410?
Google's documentation handles all 4xx codes except 429 the same way: content is treated as nonexistent and indexed URLs are removed. For a buyer, what counts is that missing pages answer with a genuine 4xx code.
What is a soft 404 and how do I spot one?
The documentation describes a 2xx page that is empty or shows an error message as a soft 404. Open a made-up address on the site. If the page says not found but the status is 200, the problem exists.
What is the difference between permanent and temporary redirects?
301 and 308 are strong signals that the target should be processed, while 302, 303 and 307 are weak. With a permanent redirect the new target appears in results, and with a temporary one the source page stays.
How many redirect hops are too many?
The status code documentation says Google's crawlers follow up to 10 hops by default, and the redirects page gives no figure for chain length. If you see more than one hop, ask the seller to confirm the final address in writing.
Which tool should I use for the check?
The documentation recommends none. As a practical suggestion, read status codes and redirect steps by hand in the network tab of your browser's developer tools.
Conclusion
A publisher site's technical health reads through three things: whether server errors repeat, whether missing pages answer with a proper 4xx code, and what type of redirect the address uses and how many steps it takes. Persistent 5xx errors justify a reject, and soft 404s, mass redirects to the home page or script-based redirects justify a hold. Run the probe by hand on different days, and keep dated findings with the order note. A healthy probe does not guarantee that a link stays where it is, but it removes obvious obstacles before you pay. If you want to compare ready-made options afterwards, the backlink packages page on Akua Adforce lists scope and terms.
Post a comment
Please log in to leave a comment. Login