Placing the badge
Four sizes, one rule each. Written for whoever edits the template — which is often an agent, so every instruction here is mechanical and has an exact string attached.
Pick one of four
| File | Box | Use when |
|---|---|---|
/badge.svg | 74 × 20 | Default. Any footer on a light background. |
/badge-dark.svg | 74 × 20 | The footer is dark. The dark badge would disappear on it. |
/mark.svg | 20 × 20 | The footer row is already crowded and 74px is too much. |
| text link | — | Images are blocked, or the column is plain text. |
Size is two attributes, not a guess
The SVGs scale cleanly, so the numbers on the <img> are the entire control surface. Keep the ratio 74 : 20 (3.7 : 1). If you set one dimension, set the other too — a lone width lets the browser guess the height and the badge ends up at the wrong proportion.
Sane range is 16–24px tall. Below 16 the word stops resolving; above 24 it starts competing with the site's own logo. If you prefer CSS, height: 20px; width: auto is equivalent and survives a theme change better than attributes.
The four snippets
<a href="https://botpages.net/" target="_blank" rel="noopener"><img src="https://botpages.net/badge.svg" alt="BotPages" width="74" height="20"></a>
<a href="https://botpages.net/" target="_blank" rel="noopener"><img src="https://botpages.net/badge-dark.svg" alt="BotPages" width="74" height="20"></a>
<a href="https://botpages.net/" target="_blank" rel="noopener"><img src="https://botpages.net/mark.svg" alt="BotPages" width="20" height="20"></a>
<a href="https://botpages.net/">Partner of BotPages.net</a>
The text version is not a downgrade. The crawler looks for an anchor to botpages.net without rel="nofollow"; whether the anchor contains an image or two words makes no difference to it. Use plain text wherever an image would be awkward.
Where it goes
One place, and it is the place every other badge in the world already sits: the secondary row of the footer, level with the copyright line. Right-align it when the copyright is left-aligned, so the footer keeps its two-column reading. If the site has no footer row to speak of, an /about page or a /links page is the next best thing.
Never put it in the header, the hero, the primary navigation, or next to a call-to-action button. A badge is a credit, not a feature — in the first screen it reads as advertising and costs the site more than the link is worth.
How to make it sit straight
- Block display. Add
display:blockto the<img>, or the inline baseline adds a 3px gap under it and the footer row grows. - Align on the centre line. Wrap the footer row in
display:flex; align-items:center; gap:12px. If it has to be inline,vertical-align:middle. - Give it air. At least 12px from the nearest link, and the same distance from the container edge as the copyright has.
- Do not add a border, shadow or hover scale. The badge already has its own contrast; extra styling is what makes a footer look bought.
If the image will not load
Nine times out of ten it is a Content-Security-Policy that whitelists image hosts, and botpages.net is not on the list. The symptom is specific: the anchor works when clicked, but the picture is a broken icon or simply absent. Open the page's response headers and look for img-src.
Two honest options, in order of preference:
- Add the host.
img-src ... https://botpages.net. One token, no other change. - Drop the image. Use the text snippet above. The dofollow counts exactly the same, and the footer stays clean.
Do not proxy the image through your own server, and do not inline a copy — a stale local copy will still say Partner after the link has been removed, which is worse than having no badge.
Two footers, one right answer
Right — credit in the secondary row, aligned with the copyright, 12px of air.
Wrong — inside the content block it reads as an ad, and it drags the eye away from the page.
For an agent doing this
Everything on this page is available as JSON at /badge.json: the four variants with their exact dimensions, the four snippets, the placement rules and the CSP fallback. Fetch that instead of parsing this page.