FUUCKGOOGLE

English

Docs

FuuckGoogle is built around one non-negotiable principle: search results must earn their position — they cannot buy it.

This documentation explains how to use FuuckGoogle, how search results are processed, which limitations currently apply, how the service is protected, and how users can report problems or help build the project.

Quick start

Enter your query in the search field.
Choose the language mode that best fits the search.
Select Search.
Review the first ten results.
Select Show 10 more results when additional results are available.

Open FuuckGoogle Search

FuuckGoogle does not sell advertising positions, sponsored listings, paid inclusion, or ranking advantages.

Language settings

Browser language preferred

This is the recommended setting for most searches. Results matching your browser language are prioritized, while highly relevant sources in other languages may still appear.

Browser language only

This setting applies a stricter language preference. It can be useful when you specifically need results in your browser language, although it may reduce the number and diversity of available sources.

All languages

This setting allows results from all supported languages. It can be useful for international topics, technical documentation, research, proper names, and searches where the strongest source may not be available in your primary language.

Language settings affect the current search. They are not intended to create a permanent behavioral profile.

How search results are processed

FuuckGoogle retrieves candidate results from the configured search provider and processes them before presenting the final result list.

Processing may include:

Normalizing URLs
Removing duplicate entries
Limiting unnecessary repetition from the same domain
Applying source-diversity rules
Respecting the selected language mode
Applying optional AI-assisted relevance evaluation
Selecting the results shown to the user

Equivalent or substantially similar searches may be cached temporarily to improve speed, reduce unnecessary requests to external services, and protect operating capacity.

The exact order of results may vary because of language settings, source diversity, result freshness, external-provider coverage, caching, and optional relevance processing.

Ranking principles

FuuckGoogle is developed around the following ranking principles:

Relevance before revenue: no result can purchase a higher position.
No sponsored-result layer: advertisements are not inserted into the result list.
No paid inclusion: payment cannot guarantee that a website appears.
Source diversity: one company or publishing network should not dominate a general result page without a valid reason.
Language context: the selected language mode should be respected.
Original information: strong primary sources should be preferred over low-value copies where this can be determined reliably.
Freshness when it matters: outdated material should not dominate searches where current information is important.
Reviewable rules: important ranking behavior should be open to testing, criticism, and improvement.
No donor influence: donations, grants, sponsorships, and infrastructure support must remain separate from ranking.

These principles describe how the project is intended to operate. They do not mean that every result set will already be perfect. Search quality must be tested, measured, challenged, and improved continuously.

Read more on the Why We Exist and Features pages.

Source diversity

For broad searches, FuuckGoogle normally tries to prevent one website, company, or content network from occupying an unreasonable share of the first result set.

Source-diversity processing helps reduce:

Repeated pages from the same domain
Near-duplicate articles
Several subdomains controlled by one organization appearing as unrelated sources
Large publishers occupying most of the first screen
Copied or rewritten pages crowding out the original source
Several results that provide substantially the same information

Source diversity is not an absolute restriction. A navigational query, company name, software-documentation search, or explicit domain query may legitimately require several results from the same source.

Optional AI assistance

FuuckGoogle may use optional AI-assisted processing to compare a limited set of candidate results and improve their order.

The AI layer may evaluate factors such as:

How closely a result matches the apparent search intent
Whether the title and description accurately represent the page
Whether the result fits the selected language mode
Whether different results provide genuinely different information
Whether a source appears original or derivative
Whether a strong primary source should outrank a weaker summary

AI assistance cannot create paid positions, sponsored placements, or ranking privileges.

AI systems may still misunderstand queries, produce inconsistent judgments, or overestimate weak sources. Their usefulness must therefore be tested rather than assumed.

FuuckGoogle remains functional when optional AI-assisted ranking is disabled or unavailable.

External providers

FuuckGoogle does not yet operate a complete independent web index. External services may therefore be used to retrieve candidate results or provide optional relevance processing.

The currently supported providers include:

Brave Search API — used to retrieve candidate web results.
OpenAI API — used only when optional AI-assisted reranking has been enabled by the FuuckGoogle operator.
Cloudflare Turnstile — may be used to protect public functions against bots and automated abuse.

The use of external providers should be disclosed openly. Provider relationships must never purchase ranking influence or special visibility.

More information is available on the Privacy page.

Current limitations

FuuckGoogle is under active development and does not yet operate a fully independent crawler and web index.

The current service may depend partly on external search and technology providers. This can affect coverage, availability, language quality, descriptions, and which pages are available as candidate results.

Current limitations may include:

Relevant pages missing from the available index
Incomplete coverage in some languages or regions
Temporary external-provider outages
API request limits
Imperfect detection of copied or repetitive content
Imperfect grouping of related domains and organizations
Result snippets that do not fully describe the linked page
Weak freshness signals for some time-sensitive queries
Occasional ranking mistakes from optional AI processing

The long-term direction is to develop more independent crawling, indexing, evaluation, and ranking infrastructure while keeping the system open to public inspection and contribution.

Privacy

FuuckGoogle is designed to minimize unnecessary data collection and avoid advertising profiles.

Technical information may be processed temporarily when necessary to complete a search, prevent abuse, apply rate limits, diagnose errors, or protect the service.

Search activity is not intended to be used to:

Target advertisements
Create commercial interest profiles
Determine purchasing power
Allow sponsors to target individual users
Sell user attention to third parties

External providers may process the limited information required to complete a request. Their use should be disclosed, reviewed, and limited to what is reasonably necessary.

Read the full Privacy page or open the privacy contact form.

Service protection

FuuckGoogle uses reasonable protections against automated abuse, spam, excessive requests, scraping, and activity that could reduce availability for genuine users.

These protections may include:

Temporary request limits
Short-term request counters
Search-response caching
Automated abuse checks
Human-verification challenges
Honeypot fields on public forms
Temporary security tokens

When a temporary limit is reached, the displayed message should explain what happened and, where possible, approximately when the user can try again.

Exact security rules and thresholds are not published because doing so would make them easier to bypass.

Reporting problems

A useful search-quality report should include:

The complete search query
The selected language mode
The result that appears problematic
A clear explanation of the problem
A stronger result or source where available

Technical support: broken searches, interface errors, language problems, or missing functionality
Abuse, spam, or misuse: manipulation, malicious automation, spam results, or misuse of the service
Privacy and data: questions about processing, retention, external providers, or personal information
Security vulnerability: active vulnerabilities or sensitive operational issues that should be reported privately
Sponsorship and infrastructure: grants, hosting, infrastructure, or financial support without ranking influence
General enquiry: anything that does not fit the categories above

A report does not automatically remove, demote, or block a website. Reports should become evidence for improving general rules rather than a private method for penalizing a competitor.

Development and contributions

Development should take place through public issues, discussions, separate branches, documented tests, and reviewed pull requests.

No contributor should make unreviewed changes directly to the production search engine.

Code of Conduct

FuuckGoogle should make room for strong opinions, rigorous criticism, and honest technical disagreement without allowing harassment, intimidation, or personal attacks.

Expected behavior

Discuss ideas, evidence, and technical outcomes rather than attacking people.
Treat contributors with different backgrounds and experience levels respectfully.
Explain objections clearly and allow others a reasonable opportunity to respond.
Disclose relevant commercial, organizational, or personal conflicts of interest.
Respect privacy, security, embargo, and responsible-disclosure procedures.
Give appropriate credit for code, research, writing, testing, design, and other work.
Accept that maintainers may reject a contribution for technical, legal, security, or project-scope reasons.
Help create an environment where new contributors can participate.

Unacceptable behavior

Harassment, threats, stalking, discrimination, or targeted intimidation
Personal attacks or publishing private information without permission
Deliberate disruption of discussions or development systems
Spam, vote manipulation, false reports, or coordinated attempts to target a website or contributor
Using money, employment, status, or personal relationships to demand ranking influence
Public disclosure of an active vulnerability before maintainers have had a reasonable opportunity to respond
Submitting malicious code, hidden tracking, credential theft, or deliberately deceptive functionality

Enforcement

Project maintainers may edit or remove content, reject contributions, restrict participation, or ban accounts when behavior threatens contributors, users, security, or the integrity of the project.

Enforcement decisions should be proportionate, documented where appropriate, and protected from donor, sponsor, advertiser, and commercial influence.

Report Code of Conduct concerns through the general contact form. Use the private security form when a report contains vulnerability details or other sensitive operational information.

Responsible security disclosure

Do not publish active vulnerabilities, credentials, private keys, exploitable endpoints, or detailed attack instructions before the issue has been reviewed.

A useful private security report should include:

A clear description of the issue
The affected component or page
The steps required to reproduce it
The likely impact
Relevant logs, screenshots, or proof-of-concept material
Any suggested mitigation

Submit a private security report

Security reports must not be used to demand payment, ranking changes, publicity, access to private systems, or control over the project.

Frequently asked questions

Does FuuckGoogle show advertisements?

No. Advertising and sponsored-result positions are not part of the FuuckGoogle result page.

Can a company pay to rank first?

No. Donations, sponsorships, infrastructure support, memberships, and partnerships must not affect inclusion, visibility, or ranking.

Does FuuckGoogle currently operate its own complete web index?

Not yet. The current service still depends partly on external providers while more independent infrastructure is developed.

Why can FuuckGoogle results differ from other search engines?

Differences can result from language settings, source-diversity rules, duplicate removal, caching, optional relevance processing, external-provider coverage, and the absence of paid placements.

Why am I seeing error 429?

Error 429 means that a temporary request limit has been reached. The accompanying message should explain approximately how long to wait before trying again.

Why is a human-verification check shown?

A verification challenge may appear when traffic looks automated or unusual, or when a temporary protection threshold has been reached.

Does FuuckGoogle build an advertising profile from my searches?

No. Search activity is not used to create advertising profiles or sell targeted access to users.

Can I request that a competitor be removed?

No. You may report spam, manipulation, copied material, misleading information, or a weak result set, but reports do not provide a private removal or demotion service.

Can donors influence search results?

No. Financial support must remain completely separate from search inclusion, exclusion, visibility, and ranking.

How can I contribute?

Developers, testers, researchers, writers, translators, designers, privacy specialists, security reviewers, and infrastructure contributors are welcome. Visit the Contribute page.

How can I support the project financially?

Visit the Donate page. Financial support never purchases ranking influence.

Built in the open. Ranked by relevance. Never by money.