Contribute
FuuckGoogle is being built in public — and building a better search engine requires much more than code.
building a better search engine requires much more than code.
Our goal is to create an open, useful, and genuinely independent search engine where advertisements cannot buy attention, sponsors cannot purchase influence, and corporations cannot quietly control what people find.That is a serious undertaking. It requires developers, researchers, designers, language specialists, privacy experts, infrastructure engineers, search professionals, writers, testers, and ordinary users willing to challenge weak results and improve the system.
Everyone can contribute. Nobody can buy control.
Help build the alternative
FuuckGoogle should not be shaped behind closed doors by one company, one founder, one investor, or one small technical team.
The project is intended to grow through public discussion, documented decisions, open-source development, measurable search-quality testing, and contributions from people with different skills, experiences, languages, and perspectives.
You do not need to understand the entire search engine before getting involved. Many of the most valuable contributions begin with one clearly identified problem and one well-tested improvement.
Contribute code
Developers can help build, review, and improve areas such as:
- Search-result retrieval and processing
- Ranking and optional reranking systems
- Source diversity and duplicate detection
- Language and contextual relevance
- Web crawling and indexing
- Query understanding and normalization
- Spam and manipulation detection
- Frontend and responsive interface development
- Accessibility
- Public APIs and integrations
- Performance, caching, and reliability
- Server infrastructure and deployment
- Automated testing
- Privacy and security
Code contributions should normally be submitted through the public source-code repository as issues, discussions, proposed changes, or pull requests.
Source-code repository: View FuuckGoogle on GitHub
How code contributions work
No individual contributor can directly change the official search engine.
A typical contribution process may include:
- Find or create a public issue describing the problem.
- Discuss the proposed approach when the change is substantial.
- Develop the change in a separate branch or fork.
- Add relevant tests and documentation.
- Submit a pull request for public review.
- Allow maintainers and contributors to examine the change.
- Respond to feedback and verify that existing functionality still works.
- Test the change outside the production environment.
- Deploy only after the required reviews and approvals are complete.
This process protects both the project and the people who depend on it.
Open source means open participation — not uncontrolled production access.
Improve search quality
You do not need to write code to help improve FuuckGoogle’s results.
Search-quality contributors can test real queries and report problems such as:
- An irrelevant result ranking too highly
- An important or authoritative source being absent
- Several results containing substantially the same information
- One company or publishing network dominating the results
- A copied article appearing above the original source
- A result matching the wrong language or context
- A misleading title or description
- Outdated information appearing above a current source
- Spam, manipulation, or low-value generated content
A useful report should explain what appears to be wrong and, where possible, identify a stronger result or source.
Reports must never automatically remove or penalize a website. They should become evidence for improving general ranking principles — not a weapon for silencing competitors or viewpoints.
Report a search-quality problem: Open the technical support form
Report spam, manipulation, or misuse: Open the abuse report form
Help create public search tests
Ranking changes should be evaluated against documented test queries rather than the preferences of one individual or organization.
Contributors can help build public evaluation sets covering areas such as:
- General information searches
- Local and regional services
- Technical documentation
- Research and academic information
- Current events
- Government and public information
- Product and comparison searches
- Health and safety information
- Different languages and regions
- Rare or highly specific queries
- Spam and manipulation attempts
Each evaluation should explain what a useful result looks like, which sources appear authoritative, and why one result may deserve to rank above another.
The purpose is not to force every query into one rigid formula. It is to make changes measurable, reviewable, and less dependent on the instincts of a small group.
Contribute language and regional expertise
Search quality depends heavily on language, culture, terminology, and local context.
Language contributors can help with:
- Interface and documentation translations
- Spelling and query normalization
- Synonyms and alternative expressions
- Local names and place references
- Regional search intentions
- Grammar and compound words
- Language detection
- Region-specific terminology
- Evaluation of local-language results
A global search engine cannot assume that every language behaves like English or that every region searches for information in the same way.
Native speakers and local experts are essential to making FuuckGoogle genuinely useful across languages and communities.
Contribute design and accessibility
A search engine should be clear, fast, readable, and easy to use.
Designers and accessibility contributors can help improve:
- The search interface
- Desktop, mobile, and tablet layouts
- Keyboard navigation
- Screen-reader support
- Color contrast
- Text size and readability
- Focus states
- Result scanning and spacing
- Language controls
- Error messages and empty states
- Public design documentation
The interface can have a strong identity without becoming slow, distracting, or difficult to navigate.
Search remains the product. The design should help people reach useful information rather than compete with it.
Contribute documentation
Good documentation allows more people to understand, test, and improve an open-source project.
Writers and technical contributors can help create and maintain:
- Installation guides
- Developer setup instructions
- Architecture documentation
- API references
- Ranking-principle explanations
- Governance documents
- Privacy documentation
- Contributor guides
- Release notes and changelogs
- Frequently asked questions
- Translations
Documentation should be written for the person who does not already know how the system works.
Project documentation: Read the FuuckGoogle documentation
Contribute privacy and security expertise
Privacy and security must be built into the project from the beginning. They cannot be added later as marketing language.
Relevant contributions include:
- Security reviews
- Threat modeling
- Responsible vulnerability disclosure
- Data-minimization reviews
- Logging and retention recommendations
- Rate limiting and abuse prevention
- Dependency audits
- Authentication and access control
- Privacy-notice reviews
- Assessment of external providers
Active vulnerabilities and sensitive operational details should be reported privately before public disclosure.
Security contact: Report a vulnerability privately
Privacy contact: Open the privacy contact form
Contribute infrastructure
A useful search engine requires fast, reliable, secure, and resilient infrastructure.
Organizations and experienced infrastructure contributors may help with:
- Hosting and server capacity
- Content delivery and caching
- Monitoring and reliability
- Database and index storage
- Web-crawling infrastructure
- Testing environments
- Backups and disaster recovery
- Geographically distributed services
- Performance optimization
Infrastructure support must never purchase influence over search results, ranking decisions, governance votes, or the visibility of the provider’s own websites.
Infrastructure partnerships: Contact us about infrastructure support
Financial support
Search infrastructure, external APIs, development environments, storage, monitoring, security, and public services all cost money.
FuuckGoogle may be supported through methods such as:
- Individual donations
- Memberships
- Research and technology grants
- Non-profit foundations
- Transparent infrastructure sponsorships
- Paid API access
- Hosted private search installations
Financial support must remain completely separate from search inclusion, exclusion, and ranking.
No payment can provide:
- A higher search position
- Guaranteed inclusion
- Removal of a competitor
- Preferential ranking treatment
- Special influence over search-quality decisions
- Hidden control over the project
Major financial contributions and their intended purpose should be disclosed publicly.
Support the project: View funding and membership options
Grants and partnerships: Contact us about financial support or partnerships
Governance matters
Publishing source code is not enough to guarantee an independent search engine.
FuuckGoogle also needs transparent governance capable of preventing a future owner, investor, sponsor, or leadership group from quietly abandoning the project’s founding principles.
The governance system should define:
- How maintainers are selected
- Who can approve code changes
- How major technical decisions are made
- How ranking-policy changes are reviewed
- How conflicts of interest are disclosed
- How financial contributions are reported
- How community members can challenge or appeal decisions
- How the no-advertising and no-paid-ranking principles are protected
The long-term goal should be an independent structure capable of protecting the domain, identity, infrastructure, source code, and founding principles from commercial capture.
Code of conduct
FuuckGoogle should allow strong opinions, rigorous criticism, and honest disagreement.
It should not tolerate harassment, discrimination, threats, personal attacks, deliberate disruption, or attempts to manipulate the project for private commercial advantage.
Contributors are expected to:
- Challenge ideas and evidence rather than attack people
- Explain technical objections clearly
- Disclose relevant conflicts of interest
- Respect privacy and security procedures
- Avoid manipulating discussions for commercial benefit
- Give appropriate credit to the work of others
- Help new contributors participate
Code of Conduct: Read the project rules
Recognition
People who make meaningful contributions should receive visible credit for their work.
Recognition may include:
- Git commit history
- Contributor listings
- Release notes
- Maintainer status
- Public project updates
- Founding-contributor recognition
Recognition should reflect real work and responsibility — not payments, personal status, or private connections.
Start here
Choose the type of contribution that best matches your skills or interests:
- Developers: Review open issues, inspect the code, and contribute tested improvements.
- Search testers: Submit examples of weak, misleading, or repetitive result sets.
- Language experts: Improve local-language relevance and evaluation.
- Designers: Review usability, responsive behavior, and accessibility.
- Writers: Improve documentation and explain complex systems clearly.
- Privacy and security specialists: Review data handling, abuse prevention, and infrastructure.
- Organizations: Offer transparent technical or financial support without ranking influence.
What we are building together
FuuckGoogle is not simply an attempt to recreate an existing search engine without advertisements.
We are building a different relationship between search, money, technology, sources, and the people using the system.
A search engine where:
- The code can be inspected
- The ranking principles can be challenged
- The community can propose improvements
- Different languages and regions can be represented
- Financial support cannot purchase visibility
- No advertiser owns the first screen
- No corporation can quietly buy control
Help us build the search engine people should be able to trust.
Built in the open. Ranked by relevance. Never by money.