Noindex vs. Nofollow: Differences, Examples, and SEO Best Practices for 2026

Published: 28 Oct 2026

Understanding noindex vs. nofollow helps you decide which pages should appear in search results and how to qualify links on your website. In this guide, you’ll learn the differences between these controls, when to use each, and how to implement them through robots meta tags, HTTP headers, and link attributes.

We’ll explore practical examples for service websites, blogs, and online stores, explain how robots.txt and canonical tags fit into your decisions, and show you how to check your implementation. You’ll also find common mistakes to avoid, troubleshooting tips, and 10 FAQs, with recommendations based on Google guidance available in 2026.

Noindex vs. Nofollow: The Main Difference

The easiest starting point is the object you want to control: a page’s search visibility or the relationship expressed by its links.

Choose noindex when the page itself should stay out of search.
Consider nofollow when a link needs qualification.
Check whether a change belongs on one link or across an entire page.

Control	Where it goes	Main purpose	Does it exclude the page from search?
`noindex`	Robots meta tag or HTTP header	Exclude the resource from indexing	Yes, after a supporting crawler accesses and processes it
Page-level `nofollow`	Robots meta tag or HTTP header	Apply nofollow treatment to the page’s links	No
`rel="nofollow"`	Individual anchor element	Qualify that particular link	No
`rel="sponsored"`	Individual anchor element	Identify a commercial link relationship	No
`rel="ugc"`	Individual anchor element	Identify a user-contributed link	No

Noindex is an indexing rule; Google treats nofollow link qualifications as hints. Avoid interpreting nofollow as an absolute guarantee that a URL cannot be discovered, crawled, or used by Google.

For your own decisions, write down the desired outcome before touching the code. “Exclude this confirmation page” and “identify this paid recommendation” are different requirements, even when both occur on the same website.

Understand Crawling, Indexing, and Ranking First

These three stages explain why a page can behave differently from what you expect. Troubleshooting becomes easier when you identify which stage your change addresses.

Crawling: a search engine requests a URL and reads the response.
Indexing: the search engine processes content for possible inclusion in its index.
Ranking: indexed content is evaluated for particular searches.

Robots.txt primarily controls crawler access. It is not a reliable way to exclude an HTML URL from Google’s index: a blocked URL may still be known through links elsewhere.

My recommended diagnostic order is access, page response, indexing controls, then content and ranking considerations. This stops you spending hours rewriting a page when the actual problem is a restrictive technical setting.

What Is the Noindex Meta Tag?

A noindex instruction tells supporting search engines to exclude the resource from their index. For an HTML page, place the robots meta tag inside the document’s <head>.

Use a page-specific rule for an individual exclusion.
Keep the URL accessible to Googlebot when relying on noindex.
Allow time for crawling and processing after implementation.

<head>
  <meta name="robots" content="noindex">
</head>

Google must access the resource to read this instruction. Blocking the same URL in robots.txt can prevent that, and Google does not support placing a noindex rule directly inside robots.txt.

For a small business website, I recommend documenting each excluded page and its purpose. A short note such as “confirmation after a successful enquiry” makes future reviews much easier than an unexplained setting in an SEO plugin.

When Should You Use Noindex?

Choose exclusions according to the page’s purpose and its value to search visitors. The examples below are candidates for review, rather than rules to apply automatically across every site.

Form confirmation pages: a visitor normally reaches them after completing an action.
Internal search results: assess whether generated results should be search landing pages.
Temporary public previews: useful when a page must remain accessible during review.
Selected utility pages: assess account, workflow, or other operational pages individually.
Weak archive pages: review usefulness, overlap, and opportunities for improvement first.

Google identifies low-value content as one reason a site owner might limit search exposure. However, the right editorial decision could also be to improve, consolidate, or remove the content.

For your website, I would start with pages that have a clear operational purpose. Avoid sweeping rules such as “noindex every page with fewer than 500 words”: a concise contact page may be much more useful than a long, repetitive article.

Practical Scenario: A Service Business Thank-You Page

Imagine a visitor requests a quote and lands on /thank-you/. That page should confirm the enquiry and explain what happens next.

Keep the confirmation specific and reassuring.
Provide a route back to useful service information.
Record the exclusion decision in your page inventory.

In this illustrative setup, /services/technical-seo/ is the page you would develop for prospective customers. The confirmation page has a different job: helping someone who has already contacted you.

Before changing anything, review the actual confirmation content. If it includes reusable advice that could help search visitors, consider publishing that advice on a dedicated resource page instead.

An administration login or test environment introduces an access-control question as well as a search-visibility question. Handle both deliberately.

Protect administrative functions with proper authentication.
Restrict staging access where appropriate.
Keep environment-specific settings on a release checklist.

Adding noindex to an admin login does not secure the login, hide its address from everyone, or prevent direct visits. For confidential material, use access controls; Google explicitly describes password protection as a way to restrict access.

For a setup like the original dgaps.com example, I would document the login page separately from the pages behind it. That distinction helps the business owner explain the requirement accurately to a developer.

How to Implement Noindex Correctly

Choose an implementation method that suits the resource and your publishing system. The setting should be verifiable in the response delivered to visitors and crawlers.

Use an HTML meta tag for individual HTML pages.
Use an HTTP response header when that fits your server configuration.
Check templates and shared rules before applying changes at scale.

For a PDF or another non-HTML resource, an HTTP header can carry the instruction:

X-Robots-Tag: noindex

The X-Robots-Tag supports robots rules at the HTTP response level. Google also applies the more restrictive rule when robots instructions conflict, so an additional permissive setting does not cancel an existing restriction.

I recommend testing one representative URL before changing an entire folder. Save the original configuration and note the scope, so you can reverse an unintended change quickly.

Using CMS Settings Without Losing Control

Your CMS may expose search visibility settings instead of requiring a manual HTML edit. The field label is only the starting point; the delivered page is what matters.

Confirm whether the setting affects one page or a whole content type.
Check inherited template settings.
Review server and CDN rules if the output differs from your selection.

Google notes that CMS platforms can provide mechanisms for managing robots meta tags. Because interfaces vary, use your platform’s current documentation for the exact control.

A useful handover note includes the URL, intended setting, implementation location, and person responsible. This gives the next editor enough context to avoid undoing a deliberate choice.

JavaScript Websites: Check the Initial Response

A page can look correct in your browser while sending an unsuitable indexing instruction in its initial HTML. This deserves particular attention after a redesign or framework migration.

Review the original HTML response.
Compare it with the rendered page.
Include indexing controls in deployment checks.

Google may skip rendering when it encounters noindex, so using JavaScript to remove an initial noindex can fail. An indexable page should not rely on that sequence.

For your developer brief, describe the required output directly: “The public service page must not contain a noindex instruction in its initial response.” That is easier to verify than “please fix SEO.”

What Is Nofollow, and How Do Its Two Forms Work?

Nofollow can appear at page level or on a specific link. The original guide mixed these forms, which can lead to broader changes than intended.

Page level: <meta name="robots" content="nofollow">.
Link level: an anchor with rel="nofollow".
Choose the scope before implementing the rule.

<a href="https://example.com/resource" rel="nofollow">
  Referenced resource
</a>

Google’s robots documentation defines page-level nofollow for links on the page. If only one reference requires qualification, a link-specific attribute is the more targeted implementation.

My recommendation is to make link decisions while editing the relevant sentence. Ask why the reference is included and what relationship exists, rather than assigning the same attribute to every external destination.

Nofollow, Sponsored, or UGC: Which Should You Choose?

The relationship behind the link determines the most appropriate annotation. Commercial placements, reader contributions, and independent editorial references deserve separate consideration.

Sponsored: advertising, affiliate arrangements, and compensated placements.
UGC: links contributed through comments or forums.
Nofollow: other situations where the qualification is appropriate.
Ordinary link: a trusted editorial reference without a qualifying relationship.

<!-- A commercial recommendation -->
<a href="https://example.com/offer" rel="sponsored">View the offer</a>

<!-- A reader-contributed reference -->
<a href="https://example.com/community" rel="ugc">Reader resource</a>

<!-- A user-contributed link with additional qualification -->
<a href="https://example.com/profile" rel="ugc nofollow">Contributor profile</a>

Google prefers sponsored for paid placements, while nofollow remains acceptable for them. Its outbound-link guidance also supports UGC and combinations of relationship values.

For an affiliate article, I would review the product buttons, comparison table, image links, and text recommendations together. A consistent review process is easier to maintain than remembering to qualify just the first link.

Practical Scenario: Reviewing a Sponsored Partner Mention

Suppose your service business publishes an article that includes a paid partner recommendation. Review the arrangement before deciding how the link should appear.

Confirm whether compensation or another commercial benefit exists.
Identify every link associated with the arrangement.
Include a clear reader-facing explanation where appropriate.

Google’s spam policies permit paid links when they are appropriately qualified with sponsored or nofollow.

A link attribute explains a technical relationship to search engines; a visible explanation helps your reader understand the recommendation. Keep both parts in the editorial review rather than assuming one replaces the other.

Should You Nofollow Internal Links or Pagination?

Internal navigation helps people move through your website and gives search engines routes to discover useful content. Review navigation changes carefully before adding restrictions.

Keep important service and resource links easy to find.
Use descriptive anchor text.
Avoid automatically qualifying every external reference.

Google recommends crawlable links and meaningful anchor text, and advises against applying nofollow to every external link.

For your business website, I would prioritise a clear path from educational articles to relevant service pages. That gives the visitor an understandable next step without forcing a sales link into every paragraph.

Ecommerce Scenario: Products Beyond Page One

A product collection may extend across several pages, so later pages need a deliberate discovery strategy. Treat pagination separately from optional filters and sorting variations.

Link sequential pages with ordinary crawlable anchors.
Give each page a distinct URL.
Use each paginated page’s own canonical URL.

Google recommends sequential pagination links and advises against canonicalising every page in a sequence to page one. Blanket nofollow on “next” links conflicts with the goal of making later content discoverable.

In an illustrative store review, I would sample products shown only on later collection pages. Then I would check how a shopper reaches them from the main category, rather than reviewing the category’s first screen alone.

Noindex vs. Canonical vs. Robots.txt

These tools answer different questions, so diagnose the problem before choosing one. A duplicate URL, an unwanted search result, and excessive crawler activity may need different responses.

Noindex: exclude a resource from indexing.
Canonical: suggest a preferred representative among duplicate or similar pages.
Robots.txt: manage crawler access.
Redirect: send requests to a replacement URL where appropriate.

Google recommends canonicalisation methods for duplicate URLs and specifically discourages using noindex to influence canonical selection within a site.

Consider a service page available with a tracking parameter. If the content is effectively the same, investigate canonical handling before treating the duplicate as a page that needs exclusion. Write the business requirement first: “These addresses represent the same service.”

How to Audit and Troubleshoot Your Changes

A useful audit connects the intended outcome with evidence from the live URL. Keep a small record that you can revisit after releases and content updates.

Record the URL, purpose, and expected search visibility.
Inspect the page response and any HTTP robots headers.
Compare related URLs using the same template.
Note the date and scope of each correction.

Search Console’s URL Inspection tool provides information about Google’s indexed version and offers a live test. A successful live test is not a promise that Google will index the page.

For a service business, my suggested sample includes the homepage, a service page, an article, a confirmation page, and a PDF. This covers different publishing paths without starting with an unmanageable list.

Troubleshooting Scenario: Traffic Falls After a Redesign

When an important page loses visibility after a release, compare the release with the expected behaviour. Treat timing as a clue to investigate, rather than proof of a particular cause.

Check which templates changed.
Review the initial response and headers.
Compare affected pages with unaffected pages.
Record a correction and verify the delivered result.

One possible issue is a staging restriction carried into production; another is an unexpected template rule. Test those possibilities before assuming the copy or keyword strategy caused the change.

I would keep the investigation narrow at first: one affected URL, one unaffected URL, and the configuration difference between them. Expand the review when the evidence points to a shared cause.

Keep Your XML Sitemap Aligned With Your Intent

Your sitemap should support your preferred public URLs. Include it in the same review as page visibility and canonical decisions.

Check important public URLs are represented where appropriate.
Review excluded URLs and duplicate variants.
Investigate unexpected sitemap changes after deployment.

Google recommends listing the canonical URLs you prefer to show in search, rather than every duplicate address.

A practical monthly review can be small: sample recently published pages and recently excluded pages. Check that your sitemap and editorial record tell a consistent story.

What These Controls Mean for SEO and AI Search in 2026

Indexing and link controls support a broader content strategy. Use them to express clear decisions, while continuing to invest in pages that answer real customer questions.

Review technical accessibility before expanding an article.
Add useful examples, clear explanations, and credible sources.
Keep service information accurate and specific.
Measure meaningful enquiries and sales alongside visibility.

Google says its established SEO practices remain relevant to AI Overviews and AI Mode. A supporting page must be indexed and eligible to appear with a snippet; there is no special nofollow setting that guarantees AI visibility.

For this guide, personalisation means helping you choose based on the pages your business actually publishes. Genuine experience can strengthen a future update: add a documented implementation, the checks performed, and an observed outcome when you have that evidence.

Practical Checklist Before You Publish or Deploy

Use this checklist as a review aid for the person making the change and the person approving it. Each item should correspond to something you can inspect.

Identify the page or link and write down the intended outcome.
Confirm whether the change affects one URL, one template, or the whole site.
Review the current response before editing.
Choose the appropriate indexing or link control.
Test a representative page and relevant exceptions.
Check navigation, canonical settings, and sitemap consistency.
Record the change, owner, date, and verification result.
Revisit the result after search engines have had time to process it.

My recommendation is to attach this record to your normal publishing or release process. A small, repeatable check is easier to maintain than an occasional audit with no named owner.

For larger websites, group the work by template and business purpose. Keep exceptions visible so that a valuable archive, product collection, or resource is not swept into an unsuitable blanket rule.

Frequently Asked Questions About Noindex and Nofollow

These 10 answers address the decisions readers are most likely to face while updating a website. Each answer keeps the focus on a specific action or distinction.

1. What is the difference between noindex and nofollow?

Noindex addresses whether a page should appear in a search engine’s index. Nofollow addresses link treatment and can be applied at page or individual-link level. Choose according to your intended outcome, then verify the implementation.

2. Can I use noindex and nofollow on the same page?

Yes, both values can appear in one robots meta tag, such as <meta name="robots" content="noindex, nofollow">. Each value addresses a different concern. Before combining them, confirm that both restrictions are appropriate for the page.

3. Does noindex stop Google from crawling a page?

No, Google must access the resource to read its noindex instruction. A robots.txt block can interfere with that process. Check access and indexing controls together when an exclusion does not behave as expected.

4. Can a nofollow link lead to an indexed page?

Yes, nofollow does not exclude the destination from search. Google can discover that destination through other routes, and nofollow is a hint. Review the destination’s own indexing controls if you own it and want it excluded.

5. Should affiliate links use nofollow or sponsored?

Google prefers sponsored for commercial links, including affiliate arrangements. Nofollow remains acceptable for paid links. Review all commercial placements consistently rather than annotating only the first product link.

6. How long does Google take to process noindex?

There is no universal processing time to promise. Google needs to revisit and process the URL, and infrequently crawled pages can take longer. Use Search Console to investigate the observed state rather than assuming the change took effect immediately.

7. Can I remove noindex and make a page eligible again?

Yes, remove the unwanted restriction from every applicable location. Check for a restrictive HTTP header or inherited setting as well as the visible meta tag. Then verify accessibility and use Search Console to investigate eligibility, remembering that eligibility does not guarantee indexing.

8. Should I use noindex for duplicate content?

First decide whether you want exclusion or consolidation. Canonicalisation is generally the appropriate topic to investigate when multiple addresses represent the same content. Avoid adding noindex automatically to every duplicate-looking URL.

9. Should I nofollow pagination links?

Generally, keep pagination links crawlable so later pages can be discovered. Google recommends sequential links and separate URLs for the sequence. Review optional filters independently instead of treating every collection variation as the same problem.

10. Will noindex or nofollow automatically improve rankings?

Neither setting promises a ranking increase. Their value comes from matching the control to a real publishing requirement. Assess the result through correct visibility, useful navigation, and business outcomes rather than expecting an automatic traffic lift.