ecosia.org No paid content found

A search engine is software that finds and ranks web pages in response to a query. It works in four stages: crawling (discovering pages), indexing (storing and organizing what was found), ranking (ordering results by relevance and quality), and serving (displaying the results page). You use one by typing a query into a search box and refining it based on what comes back. General engines like Google or Bing index the whole web; specialized engines focus on a niche — Ecosia, for example, is a general search engine that directs its profits toward tree planting and renewable energy projects.

The four core jobs of any search engine

Every engine, from a global one to a site-specific search box, performs the same basic pipeline:

The key takeaway: ranking only happens over pages that were crawled and indexed. If a page is missing from results, the problem is usually earlier in the pipeline, not the ranking step.

What happens between your query and the results page

1. You type a query. The engine parses it into terms and intent signals — is this a question, a navigational request, or a comparison?
2. It matches against the index. Candidate pages are pulled from the stored index rather than from the live web, which is why results reflect the index's snapshot.
3. It ranks the candidates. Ranking blends relevance (does the page match the words and intent?) with quality signals (links, freshness, usability, and more).
4. It builds the results page. Each result gets a title, URL, and snippet; extra elements like ads, knowledge panels, and filters are layered on top.
5. You refine. Most searches are iterative — you adjust wording, add qualifiers, or use filters until the results are useful.

General vs. specialized vs. eco-focused engines

• General engines index broadly and aim to answer almost any query. Google, Bing, and Ecosia fall here.
• Specialized engines narrow the index to a domain — academic papers, code, shopping, or a single website's content.
• Eco-focused engines are general engines with a distinct business model. Ecosia describes itself as a search engine and AI that uses 100% of its profits for the planet, supporting tree planting and renewable energy projects. The search experience is familiar; the difference is where the revenue goes.

If your goal is simply the best answer, a general engine is usually the right tool. If you want your search activity to fund environmental projects, an eco-focused general engine like Ecosia is a direct substitute — same workflow, different destination for profits.

Reading a results page: what each element tells you

• Snippets — the short excerpt under each title. They preview how the page matches your query, but they're generated, not always verbatim.
• Ads — paid placements, typically labeled. They can be relevant, but their position reflects payment as well as quality.
• Knowledge panels — summarized facts pulled from structured sources, useful for quick lookups but worth verifying on the source page.
• Filters and tabs — tools to narrow by type (images, news, maps), date, or region. They change which slice of the index you're searching.

Practical tips for better queries and results

• Be specific. "best budget mirrorless camera 2024" beats "camera."
• Use the engine's operators. Quotation marks for exact phrases, minus signs to exclude terms, and site: to restrict to one domain.
• Check the source, not just the snippet. Snippets can strip context; open the page before trusting a claim.
• Iterate deliberately. If the first page misses, change one variable at a time — wording, filters, or scope — so you learn what worked.
• Match the engine to the task. Use a specialized engine when your query lives in one domain, and a general or eco-focused engine for everything else.

The practical test for any engine is the same: does it return pages that answer your question, and can you tell why each result is there? Once you understand crawling, indexing, ranking, and serving, you can judge results instead of just consuming them.

Search engines work in three separate stages: discovery, crawling/indexing, and ranking. A page can fail at any one of them, and each failure has a different fix. If your page isn't showing up, the fastest path is to check the stages in order — don't jump straight to "ranking factors" before you've confirmed the page is even indexed.

This guide walks through each stage, what blocks it, and a step-by-step diagnostic sequence you can run with free tools.

Stage 1: Discovery — How Search Engines Find Your URLs

Before a search engine can crawl a page, it has to know the URL exists. There are four main discovery paths:

• Links from other sites (external backlinks)
• Internal links from pages already known to the search engine
• XML sitemaps you submit
• Redirects and canonical signals pointing to the URL

What blocks discovery

• Orphan pages: no internal links point to them, and no sitemap includes them. These are effectively invisible.
• Sitemap errors: a sitemap that lists non-canonical URLs, returns errors, or isn't referenced in robots.txt.
• Noindex on linked pages: if the only page linking to your target is itself excluded, the crawler may never follow the path.

Practical fix

1. Add at least one contextual internal link from a page that is already indexed.
2. Confirm the URL appears in your XML sitemap and that the sitemap is submitted.
3. Check robots.txt doesn't disallow the path.

Stage 2: Crawling and Indexing — Getting the Page Stored

Crawling means the bot fetches the page. Indexing means the content is stored and eligible to appear in results. These are not the same thing — a page can be crawled but not indexed.

Common crawl blockers

Common indexing blockers (page is crawled but not stored)

• Thin or duplicate content: near-identical to another URL on your site.
• Canonical tag pointing elsewhere: you're telling the engine "index that page instead."
• Soft 404: page returns 200 but looks empty or error-like.
• Wrong canonical chosen by the engine: often caused by conflicting signals (sitemap says A, canonical says B).

How to check index status

Use a site: query in the search engine (for example, site:example.com/page) as a rough check. It's not exact, but it tells you whether the URL is in the index at all. For a more structured view, use the search engine's own webmaster console if you have one — that's the authoritative source for coverage status.

Stage 3: Ranking — Why an Indexed Page Still Doesn't Appear

Once a page is indexed, ranking depends on relevance and authority signals. The main on-page levers:

Title and headings

• The title tag is still one of the strongest relevance signals. Put the primary topic near the front.
• H1 and subheadings should reflect what the page actually covers, not keyword-stuffed variants.
• Mismatch between title and body content is a common reason a page ranks for nothing.

Content depth and intent match

• Does the page answer the question the searcher is asking? A page about "search engines" that only defines the term will lose to a page that explains crawling, indexing, and ranking.
• Cover the subtopics a searcher would expect. Thin coverage on a broad topic rarely ranks.

Internal links and authority

• Internal links pass context and relative importance. A page with no internal links is treated as low priority.
• External backlinks still matter, but quality and relevance outweigh raw count.

Technical signals

• Mobile rendering: if the mobile version hides content, rankings suffer.
• Core Web Vitals: page experience is a tiebreaker, not a primary driver, but poor performance can hurt.
• HTTPS and clean URL structure: baseline expectations.

A Step-by-Step Diagnostic Sequence

Run these in order. Stop when you find the failure point.

1. Is the URL in the index? Run site:yourdomain.com/page. If nothing appears, go to step 2. If it appears, skip to step 5.
2. Is it blocked by robots? Check robots.txt for a Disallow rule matching the path. Check the page's meta robots and HTTP X-Robots-Tag.
3. Is it discoverable? Confirm the URL is in your sitemap and has at least one internal link from an indexed page.
4. Is it canonicalized elsewhere? Check the rel="canonical" tag. If it points to a different URL, that URL is the one being indexed.
5. Is it indexed but not ranking? Compare your title and H1 against the query. Check whether the page covers the subtopics the top results cover.
6. Check backlinks and keyword position. Free tools like the ones on SmallSEOTools.com can give you a backlink overview and keyword position tracking. Treat these as directional signals, not precise measurements — free backlink and rank tools typically sample data and can differ from what a search engine's own console reports.

Common Misconceptions

"Submit the URL and it indexes instantly." Submission queues a crawl; it doesn't guarantee indexing or timing. Indexing can take hours to weeks depending on the site.

"Meta keywords help ranking." They've been ignored by major search engines for years. Don't spend time on them.

"I can guarantee a #1 ranking." No tool or service can guarantee a specific position. Rankings depend on competition, query, location, and personalization. Anyone promising a fixed position is overstating what's controllable.

"More backlinks always means better rankings." Low-quality or irrelevant links can be ignored or actively harmful. Relevance and trust matter more than volume.

"If it's indexed, it should rank." Indexing is eligibility, not promotion. A page can be indexed and still rank on page 10 because it's less relevant or less authoritative than competitors.

Quick Reference: Which Stage Is Failing?

Work through the stages in order. Most "my page won't rank" problems turn out to be discovery or indexing problems, and those are usually the fastest to fix.

Ecosia is a search engine and AI tool that commits 100% of its profits to the planet, funding tree planting and renewable energy projects. If you want a search engine that turns everyday queries into environmental funding without changing how you search, Ecosia is built for that. The trade-offs are that results are largely sourced from partner indexes rather than a fully independent crawl, and its impact claims rest on the company's own reporting.

What Ecosia Is

Ecosia positions itself as a green search engine: a general web search tool whose distinguishing feature is not the algorithm but the destination of its revenue. According to the site, it uses 100% of its profits for the planet, supporting tree planting and renewable energy projects.

That means the product is deliberately ordinary in use — you type a query, you get results — while the business model is the differentiator.

How Ecosia Makes Money and Where Profits Go

Ecosia earns revenue the same way most free search engines do: through advertising shown alongside search results. The stated commitment is that profits, not gross revenue, are directed to environmental work.

Two destination categories are named in the site's own description:

• Tree planting — the best-known Ecosia activity.
• Renewable energy projects — a second category of funding.

Because "100% of profits" is a company claim, the practical question for a user is not whether the wording is generous but whether the reporting is specific enough to check. That is covered below.

How to Use Ecosia

You do not need an account to search. The main decision is whether to use it occasionally or make it your default.

Use it in a browser

1. Go to ecosia.org.
2. Type your query into the search field and submit it.
3. Expected result: a standard results page with ads and organic listings, plus Ecosia's own interface elements.

Set it as your default search engine

Most browsers let you add a custom search engine rather than only choosing from a built-in list. The general pattern is:

1. Open your browser's settings and find the search engine section.
2. Choose to add a new or custom search engine.
3. Enter a name (for example, "Ecosia") and the search URL the browser should use for queries.
4. Set it as the default.

Expected result: queries typed in the address bar go to Ecosia instead of your previous engine. Exact menu names differ by browser and version, so treat the steps as a pattern rather than a fixed path.

Common snags

• Mobile defaults are stickier than desktop ones. Some mobile browsers restrict custom engines, so you may need Ecosia's own app or a browser that allows it.
• Extensions and profiles can override your choice. If searches keep going elsewhere, check for a search-related extension or a managed work profile.
• Switching back is easy. If you dislike the results, resetting the default takes the same steps in reverse.

Results and Privacy Compared with Mainstream Engines

The honest framing is that Ecosia is a different business more than a different index. Its results depend on partnerships with other search providers, so you should expect result quality broadly similar to those partners rather than a distinct ranking philosophy.

On privacy, the site's positioning is environmental rather than privacy-first, so do not assume Ecosia matches dedicated private search engines on every tracking question. If privacy is your primary goal, compare it directly against privacy-focused engines on the specific behaviors you care about — query logging, account requirements, and ad personalization — rather than assuming "green" implies "private."

How to Verify the Impact

Ecosia's impact claims are self-reported, so verification means reading its own reporting rather than an independent audit.

Practical checks:

• Look for a running counter or impact page showing trees funded and projects supported.
• Look for financial reports or transparency pages that separate revenue, costs, and the amount directed to projects.
• Check whether reporting distinguishes money committed from trees actually planted and surviving — these are different claims.

A useful habit: treat the counter as a marketing surface and the financial and project reports as the substance. If a number cannot be traced to a report, treat it as a claim rather than a verified figure.

Who Should Use It

Ecosia fits you if you want your existing search habit to route money toward environmental projects and you are comfortable with partner-sourced results. It fits less well if you need a uniquely independent index, if privacy is your top priority, or if you want impact verified by a third party rather than the operator.

Typo tolerance lets a search engine return relevant results even when the query contains misspellings, transposed letters, or missing characters—without you maintaining a manual list of synonyms or corrections. Faceting lets users narrow a result set by attributes such as category, brand, price range, or availability, typically shown as filterable counts alongside the results. In a hosted search service, both features run on the same index and query pipeline: typo tolerance expands which documents match, while faceting organizes how those matches are filtered and displayed. The two interact closely, and tuning one often affects the other.

What Typo Tolerance Actually Does

Typo tolerance is a matching strategy, not a spell checker. Instead of correcting the query and searching for the corrected term, the engine compares the query against indexed terms using an edit-distance threshold (commonly Levenshtein distance) and returns documents whose terms fall within that threshold.

Key mechanics:

• Edit distance budget: A query term can differ from an indexed term by a set number of insertions, deletions, substitutions, or transpositions. A common default is 1 edit for short terms and 2 for longer ones.
• Prefix matching: Many engines treat the last token in a query as a prefix, so "headph" matches "headphones" without counting as a typo.
• Per-word tolerance: Tolerance is usually applied per token, so "wirlress hedphones" can still match "wireless headphones."
• Ranking by closeness: Exact matches typically rank above typo matches, so results degrade gracefully rather than becoming noisy.

Because this works at query time against the index, you generally don't need to build synonym lists for common misspellings. You may still want synonyms for genuine vocabulary differences ("sofa" vs. "couch"), which is a separate concern from typos.

When typo tolerance helps most

• User-generated queries on mobile keyboards, where transpositions and dropped letters are frequent.
• Product catalogs with long, technical, or brand names that users rarely spell exactly.
• Internal document search where users half-remember terminology.

When to tighten or disable it

• Short or numeric queries: Order IDs, SKUs, or codes like "A102" can match unintended items when tolerance is loose. Consider disabling tolerance for numeric fields.
• High-precision domains: Legal, medical, or financial lookups may need exact matching to avoid surfacing the wrong record.
• Small alphabets or dense vocabularies: If many terms are one edit apart, tolerance can produce false positives.

What Faceting Adds

Faceting computes, for a given result set, the distribution of values across designated fields and returns counts per value. The user then applies filters, and the result set (and the facet counts) update.

A typical faceted interface shows:

Two design choices matter:

• Conjunctive vs. disjunctive facets: Within one facet (e.g., Brand), selecting two values usually means "Acme OR Nord." Across facets (Brand AND Category), selections combine with AND. Engines often let you choose whether a facet's own counts ignore its current selection, so users can still see sibling options.
• Count accuracy vs. speed: Exact counts are more expensive on large indexes. Some services offer approximate counts or cap the number of facet values returned.

Faceting is not the same as filtering. Filtering applies a condition; faceting computes and returns the available values and their counts so the UI can present choices. Most hosted services do both in one query.

How the Two Features Interact

This is where behavior gets interesting, and where default settings can surprise you.

1. Typo matches inflate facet counts. If "hedphones" matches "headphones," those documents appear in the result set and contribute to the Category and Brand counts. Users see counts that include loosely matched items.
2. Facet filters usually don't loosen. Once a user selects Brand = Acme, the query is constrained. Typo tolerance still applies to the text query, but it can't pull in documents outside the selected facet.
3. Relevance and counts can disagree. A typo-matched document might rank low but still be counted in a facet. If your UI shows "128 results" but the top 10 look unrelated, users lose trust.
4. Index size and field configuration affect both. Fields marked as facetable are often stored differently (as structured values rather than tokenized text), so you generally can't facet on the same field you use for fuzzy full-text matching without configuring it appropriately.

A practical consequence: tune typo tolerance before you tune facet counts, because the tolerance setting defines the population that faceting summarizes.

Trade-offs to Weigh

Performance notes: typo tolerance adds query-time work but is generally cheap relative to faceting, which must aggregate across the matched set. On large indexes, the dominant cost is usually facet computation, not fuzzy matching. Index size grows mainly with the number of facetable fields and stored attributes, not with tolerance settings.

A Workable Starting Configuration

If you're setting up a hosted search service and want sensible defaults:

1. Enable typo tolerance globally, with 1 edit for terms up to ~5 characters and 2 for longer terms.
2. Treat the final query token as a prefix so partial typing returns results.
3. Disable tolerance on identifier-like fields (SKU, order number, ISBN).
4. Mark only fields users actually filter on as facetable—category, brand, price, rating, availability. Avoid faceting on free-text descriptions.
5. Return facet counts for the top N values (e.g., 20–50) rather than all values.
6. Decide per facet whether counts should reflect the facet's own selection, so users can switch between brands without losing the menu.
7. Test with real misspellings from your logs or support tickets, and check whether the top results and facet counts still make sense.

Example: tuning by use case

• E-commerce catalog: High tolerance, many facets, counts that ignore the current facet's own selection.
• Documentation search: Moderate tolerance, few facets (product version, doc type), prioritize exact phrase matches.
• Internal records lookup: Low or no tolerance on IDs, tolerance on names, minimal faceting.

FAQ

Does typo tolerance replace synonyms? No. It handles spelling variation, not vocabulary differences. Keep synonyms for terms users genuinely use differently.

Why do my facet counts change when I type a typo? Because the matched document set changed. Counts are computed over whatever the query matched, including fuzzy matches.

Can I have typo tolerance without faceting? Yes. They're independent features that happen to share a query pipeline.

Is faceting the same as filtering? Filtering applies a constraint; faceting computes available values and counts. Most interfaces use both together.

Will enabling both slow down search? Faceting is usually the larger cost. Measure with your own data rather than assuming.

The short version: typo tolerance decides what counts as a match, faceting decides how matches are organized and narrowed. Configure tolerance first, keep facetable fields deliberate, and verify that the counts your users see reflect results they'd actually recognize.

A green search engine is a search engine that directs some or all of its profits toward environmental causes—most commonly tree planting, renewable energy, or climate projects—rather than distributing them to shareholders. Ecosia is the best-known example: it states that it uses 100% of its profits for the planet, supporting tree planting and renewable energy projects. You "use" one simply by setting it as your default search engine in your browser; your searches then generate ad revenue that funds those projects. The trade-off is that green engines are usually smaller than Google or Bing, so results and features can differ.

What "green" actually means for a search engine

The label describes where the money goes, not how the search works. A search engine earns revenue mainly from ads shown alongside results. A conventional engine returns that profit to shareholders; a green engine commits it to environmental spending.

Ecosia's own description is the clearest reference point: a search engine and AI that uses 100% of its profits for the planet, supporting tree planting and renewable energy projects. That gives you two things to check in any green engine:

• The commitment: what share of profits, and to what causes.
• The mechanism: how the money is generated (ads, subscriptions) and how it reaches the projects.

How to verify a search engine's environmental claims

Marketing language is easy to write, so look for evidence you can inspect:

• Published financial reports. A credible green engine typically publishes monthly or annual reports showing revenue and where it went.
• Nonprofit status or ownership structure. Some are owned by a nonprofit foundation, which limits profit extraction; others are for-profit with a stated pledge.
• Independent audits or third-party verification. Look for external review of tree-planting partners or financial claims.
• Named project partners. Specific organizations and locations are more checkable than vague "climate projects."

If a company makes environmental claims but publishes no financials and names no partners, treat the claim as unverified.

How to switch your default search engine

The steps are similar across browsers. The input is your browser's settings; the action is adding the engine and setting it as default; the expected result is that address-bar searches go to the new engine.

Desktop (Chrome, Edge, Firefox, Safari)

1. Open the browser's Settings.
2. Find the Search engine section.
3. Choose the green engine from the list, or add it manually using its search URL.
4. Set it as the default.

Mobile (iOS and Android)

1. In the browser app, open Settings.
2. Select Search engine.
3. Pick the green engine, or add it if it isn't listed.
4. Confirm the change, then test by searching from the address bar.

Verification: run a test search and confirm the results page is the green engine's, not your old one.

Common snags: some browsers only list a fixed set of engines, so you may need to add a custom one; changing the default in one browser doesn't change it in another; and your phone's default assistant or widget may still use a different engine.

Green vs. mainstream engines: what actually differs

The practical difference for most people is result quality and features, not the search act itself. If you rely heavily on a specific ecosystem, a green engine may feel like a downgrade in convenience.

The honest limits

• Search quality. Smaller engines may return less relevant or less fresh results, especially for niche queries.
• The ad model still applies. Your searches fund the projects through ads, so impact scales with search volume and ad rates—not with good intentions.
• Impact per search is small. Individual searches generate fractions of a cent; the effect comes from aggregate volume over time.
• Claims need scrutiny. "Green" is not a regulated term, so the burden is on you to check the reports.

A reasonable way to decide

Use a green engine as your default if you want your routine searches to fund environmental work and you can accept occasional gaps in results. Keep a mainstream engine as a fallback for queries where quality matters most. Before committing, read the engine's latest financial report and confirm the projects it names are ones you'd actually support.