Powered By and Credit Links: Footer Cleanup

The small "Theme by ..." or "Powered by ..." line in your footer is a link from every page of your site to someone else's domain. Short answer: if you did not place that link on purpose, switch it off in the settings first. If it will not switch off, find where it comes from and remove it, or replace the plugin or theme that writes it. The WordPress.org plugin guidelines require credit links in plugins to be optional and hidden by default, and Google's spam policies list links distributed through the footers and templates of many sites among its examples of link spam. If you run a blog, a shop or a company site, you can question every link in your footer in one sitting.

Spotting a credit link in the rendered page

A credit link is a link a theme, plugin or designer places on your pages to promote their own name. The anchor text may start with "Powered by", "Theme by" or "Designed by" and it points to the developer's home page. Because it lives in a template file, not in one article, it repeats on every page that uses the template. One plugin or theme decision can therefore produce hundreds of links to the same domain.

Theme footers that ship with text

The footer is the best-known place. The theme prints a developer link next to the copyright line. The same logic applies to small labels in sidebars, widget areas and page headers: if the template prints them, they appear wherever the template is used. Visible links are easy to spot. The hard ones are links styled to be invisible or links set in tiny type.

What plugins leave in the front end

Forms, share buttons, maps, comment systems and page builders can add a small attribution line under their component. The line exists in the page source while the plugin runs. Deactivating the plugin removes it, but while you keep the plugin it is rebuilt on every page load.

Hiding places by type

If you use a translated admin interface, setting names may look different from the English labels used here.

How Google's pages treat template, widget and hidden links

The Google Search spam policies (Opens in a new tab) give examples under link spam. The list includes low-quality directory or bookmark site links, widely distributed links in the footers or templates of various sites, and keyword-rich, hidden or low-quality links embedded in widgets that are distributed across various sites. The pattern the document points at is one link placed into the templates of many sites.

Read those sentences carefully. The document does not say every theme credit is spam. It gives examples of links that are widely distributed and loaded with keywords. Whether a plain "Theme by Company" line falls into that category is not something the page decides. Practical suggestion: look at the link through your own site's interest. If it helps nobody on your site and you did not choose it, removing it takes the doubt away.

Concealed text and links

The same page defines hidden text and links separately. Its examples include white text on a white background, text hidden behind an image, text positioned off-screen with CSS, font size or opacity set to zero, and hiding a link by linking only one small character, for example a hyphen in the middle of a paragraph. If a theme or plugin places a link in your footer in one of these ways without telling you, you will not see it unless you list the anchor tags in the source.

Under content injection, the document also explains that attackers can add hidden links or hidden text using CSS or HTML. That is where a credit audit meets security. An unknown link may be the documented behaviour of a product, or it may be a sign that the site was compromised. If you cannot tell which, work through the hacked-site checks; finding where a link comes from is the first step toward knowing what it is.

The limits of rel attributes

Google's page on qualifying outbound links (Opens in a new tab) describes three values. Paid links should carry sponsored, which is preferred over nofollow for them. User-generated links such as comments and forum posts take ugc. Nofollow is the general option when the others do not fit. According to the page, such links are, as a rule, not followed, and the values can be combined in a space-separated list. The page says nothing about links produced by templates or site-wide links; the documentation has no statement on that.

So adding nofollow to a credit link does not count as cleaning it up. If you can remove the link entirely, removal leaves less ambiguity than managing attributes. If you keep a link on purpose because of a paid arrangement, the article on rel labeling for publishers who sell backlinks covers the labeling question.

The plugin directory rule on credits

Guideline 10 of the WordPress.org detailed plugin guidelines (Opens in a new tab) covers this directly. It says "Powered By" displays and links in plugin code must be optional and must default to not showing on the public site. The user has to opt in through a clear and understandable choice, not through terms of use or documentation they might miss. A plugin cannot require credits or links to function.

Consent as a working test

In practice, a compliant plugin either asks you during setup or offers a settings checkbox that starts unticked. If you find a credit line on a fresh install that you never agreed to, the plugin is behaving against the guideline as written. That is a fact you can state when you contact the developer. It also tells you something about how the developer reads the rules.

Gaps in the written rules

The rule applies to plugins in the WordPress.org directory. Products distributed elsewhere may follow other terms, and the guidelines do not govern them. The guidelines also allow a service to brand its own output as it likes, as long as the service, not the plugin code, adds that branding. And the page does not address themes at all on this point; there is no statement about theme footers in the documentation. So "plugins must hide credits by default, therefore themes must too" is not something you can draw from this page. For a theme, your answer sits in the theme's own documentation and licence. If a premium theme ties its licence to keeping a credit, read the licence text before you remove anything.

Readme pages and the spam rule

Guideline 12 sets a related principle for public listing pages: they may not be used to spam. It counts unnecessary affiliate links and keyword stuffing as spam, asks for affiliate links to be disclosed and to point directly at the service, and permits moderate links to directly required products such as a theme or another plugin. That rule governs the plugin's listing, not your front end, but it shows how seriously the directory treats unannounced promotion.

Site-wide template links versus single links

A link in one article is a decision about that article. A link in a template is a decision about the whole site, taken by someone else. That shift is why the topic deserves its own audit. You cannot judge a template link by reading your articles, and you will not notice it by browsing the admin screens. You have to read the front-end source.

Practical suggestion: for each credit link, ask what it gives your site. A visitor gets nothing from it, you get nothing from it, and the developer gets a repeated link. When a link has no benefit for you and sits outside your control, removing it settles the question for good.

Questions to ask before you buy

The cheapest cleanup is the one you never need. When you choose a new theme or plugin, you can do the audit up front.

1. Open the theme's demo site in a logged-out browser and read the footer source.
2. Look in the theme documentation for a section about footer credits or copyright text.
3. Read the licence for any clause that demands the credit stay. The guidelines and Google's pages state nothing on this; the licence text decides.
4. For a plugin, read the directory description and search the support forum for threads about credits.
5. Install it on staging and compare the front-end source with the record from before the install.

The fourth step is the most direct way to see whether a plugin follows guideline 10. A credit line that was never asked about during setup and does not show in the settings does not meet the opt-in principle.

Walkthrough: comparing three templates

Example scenario: an agency checks three templates on a new client site: the home page, a product list and the cart. The home page footer shows only the theme credit. The product list also shows a short attribution from a filter plugin. The cart shows no credit at all, because it uses a different template. The agency notes the difference and records each plugin's credit state in its own row. That way "the footer is clean" is understood to be true for one template and unverified for the others.

Footer audit routine

The audit comes down to three questions: which links are on the page, where does each come from, and which ones did you place yourself? Practical suggestion: follow this order.

1. In a logged-out browser, open the home page, an article, a category page and the contact page.
2. View the page source for each and find the footer section.
3. Write down every link and the domain it goes to.
4. Next to every domain other than your own, write who added it: you, the theme, a plugin, a widget or unknown.
5. Mark the unknowns and go looking for their source.

List every outbound domain

Search the source for anchors and group the domains. Several links to the same domain point to a template as the source. If one domain on the list is one you have never heard of, start there. A browser extension or a page crawler can do this job for you; the choice of tool does not change the result, because the page source is the same.

Assign an owner to each link

Cleanup routes from safest to riskiest

There are several ways to take a link out, and their risks differ. Practical suggestion: start with the one that touches the least.

Prefer a switch over a code edit

In a plugin that follows the guidelines, the credit option can be switched off in the settings. That is the safest fix: no file is touched, and updates do not bring it back. After you switch it off, read the front-end source again, because some components keep serving old output from a cache.

Hand edits to theme files

Deleting the link from a theme file looks quick, but the next theme update may overwrite that file and bring the link back. Working through a child theme is more durable than editing the parent theme. Child themes are a topic of their own. What matters here is knowing the edit can vanish after an update, so you put a check after every update.

Swapping the source

A plugin that offers no way to switch off its credit is out of step with the guidelines. Reporting it and shopping for an alternative is the reasonable path. Replacing a theme carries a risk of lost design and features, so try the change on a staging copy first.

Links living in the database

Some links live in widget content or option tables, not in templates. If a file search turns up nothing, look at the widget and menu screens in the admin. If you search and replace in the database, back up first and change only the row that holds the link. A blind replace can damage other content.

Rule for deciding what to do with a found link

Three questions per link are enough. Did I place this link on purpose and want it there? Do I know its source, and can I switch it off with a setting? Does it add value to my content? If the answer to the first is no and you cannot find the source, you have grounds to remove the link or replace the product. If all three answers are yes, the link can stay, but write its rel value as a deliberate decision.

Walkthrough: a second-hand bookshop on a purchased theme

Example scenario: a second-hand bookshop runs its online catalogue on a ready-made theme. The owner added a reviews plugin and a newsletter form. One day she notices a "Theme by ..." line and decides to audit the footer.

At the end she writes down which link came from where and which could be switched off. Because the theme credit would not turn off through a setting, she adds a note to the inventory to check the footer again after the next update.

Proving the cleanup worked

Removal does not end when the link disappears. Another output may have taken its place, the layout may have shifted, or a cache may be serving the old version.

• Open the same four pages in a logged-out browser and read the footer source again.
• Clear the cache and repeat the check.
• Check that the footer still looks right at a phone screen width.
• Check that the title tag and the main heading did not change.
• Look for copies of the removed link on old pages.
• Run the list again after the next theme or plugin update.

Record the result in the inventory

For each plugin and theme you cleaned, record the state of the credit option, who made the change and the date. That note lets you compare when a link comes back after an update. The general settings list is in the WordPress SEO settings checklist.

Contacting the developer and handling returning links

When a credit will not switch off, the first step is a clear support request. For plugins in the WordPress.org directory, the support forum exists for this. Naming guideline 10 turns the request from a personal preference into a question about a rule. Practical suggestion: include four things.

1. The plugin version and the WordPress version.
2. The address of the page where the link shows.
3. A sentence saying you looked for an option to switch it off and found none.
4. A reference to guideline 10 and an open question about how it can be resolved.

If there is no answer or no fix, go back to the second question of the decision rule: is the source known and can a setting switch it off? If not, replacing the plugin is a reasonable choice.

After an update restores the link

A link can return with an update. Hand edits to theme files are the most exposed, because an update rewrites the file. A setting is stored in the database and survives updates, although a new version might rename the option. So reread the footer of the same four pages after each update round. If a link has returned, record the date and the version number; a record that the problem persisted in the next release makes your correspondence with the developer easier. If updates install automatically, tie the check to a calendar note, so you find the change instead of it arriving unnoticed.

Notes for agencies and multi-site owners

When you work on a client's site, you should have placed the link or the client should have agreed to it. If you leave a credit link on a site you hand over, say so in writing. If you install the same theme on many sites, the link goes to the same domain in the same form on all of them, which moves you closer to the distribution pattern in Google's examples. That is not a violation in itself, but it widens the uncertainty. For footer links that are bought, not built in, see buying footer links: sitewide risks and safe scenarios, which treats the subject as a purchase decision, while here the link is something software adds on its own.

For wider link policy questions, Google link spam policies and safe link building sets out the framework. Google's documentation can change; check the current pages before relying on them.

Frequently Asked Questions

Is deleting a theme's footer credit safe?

If you delete it in a theme file, the next theme update may bring the link back. Look for an off switch in the theme settings first, then read the theme documentation and licence. Take a backup before any edit.

Is adding nofollow to a credit link enough?

Google's page on qualifying outbound links says nofollow links are, as a rule, not followed, but it gives no separate rule for template links. If you can remove the link, removal leaves less doubt.

May a plugin show its credit link by default?

Guideline 10 of the WordPress.org plugin guidelines says credits and links must be optional and must default to not showing on the front end. A link that shows by default conflicts with that principle.

Does the same rule cover theme credits?

The guidelines govern plugins, and the page has no separate rule for theme footers. The documentation has no statement on this. Check the theme's own documentation and licence.

I found a link I do not recognise. Could the site be hacked?

It could be. Google's documentation says attackers can add hidden links using CSS or HTML. If you cannot find the source, compare with a backup and move on to a hacked-site audit.

At what interval should I audit the footer?

The documentation gives no interval. Practical suggestion: check the same four pages after every theme and plugin update.

Conclusion

Credit links look small, but because they come from template files they repeat on every page as outbound links. The WordPress.org plugin guidelines ask plugins to keep them optional and hidden by default, while theme footers fall outside that page. Google lists links distributed through the footers and templates of many sites, and hidden links, among its spam examples. Reading the source in a logged-out browser, naming an owner for every link and tying removal or replacement to a rule removes the ambiguity.

Once the footer is clean, the work that remains on the site is its content.

For a steady flow of carefully made articles, take a look at our content writing service.