Security should be built into the product, not added as a badge.
FixRank is designed to analyze websites, generate search intelligence, and prepare recommended fixes while keeping access, data handling, and user control clearly separated.
This page explains how FixRank approaches security today, what users remain responsible for, and how our security model will evolve as the platform grows.
Last updated: August 2026
A security model built around separation and control.
FixRank processes website and account information to provide audits, search intelligence, AI-assisted analysis, and prioritized recommendations. Our security approach is based on a few simple principles.
FixRank should only request the access required for the feature being used.
Website analysis, account access, billing, and future deployment capabilities should remain separate rather than sharing unnecessary privileges.
AI-generated recommendations should not become production changes simply because a model suggested them.
Security claims should reflect the product that exists today, not capabilities planned for a future release.
Protecting access to your FixRank account.
FixRank accounts are authenticated before protected product areas can be accessed. Users are responsible for keeping their login credentials confidential and for maintaining control of the email account associated with their FixRank account.
Passwords should never be displayed or stored in plain text by the application.
Password-reset requests use a controlled reset flow associated with the user's account email.
Reports, settings, usage information, and account-specific product data should be available only through authenticated sessions.
Users should use strong, unique passwords and notify FixRank if they believe their account has been compromised.
What FixRank may process.
The information FixRank handles depends on how the service is used.
Information required to create and manage a FixRank account, such as account identity and email address.
Website URLs and publicly accessible website content required to perform crawling and analysis.
Audit findings, search intelligence, semantic relationships, content findings, internal-linking findings, and generated recommendations associated with a user's account.
Technical and product-usage information needed to operate, secure, troubleshoot, and improve the service.
Subscription and payment processing may be handled through the payment provider used by FixRank.
Security and privacy are related but separate topics. See the Privacy page for fuller information about personal-data handling.
Built on established cloud infrastructure.
FixRank relies on specialist infrastructure and service providers to operate different parts of the platform. Where relevant, these services may process information on FixRank's behalf in order to provide hosting, database, authentication, payments, email delivery, AI processing, monitoring, or related functionality.
We describe provider categories rather than publishing certification claims, residency guarantees, failover architecture, or uptime targets we cannot independently evidence.
FixRank analyzes websites without requiring source-code access.
For normal website auditing, FixRank crawls publicly accessible website pages and uses the information it can retrieve from those pages to build its analysis. This means the standard audit workflow is fundamentally different from giving FixRank direct access to a production codebase or server.
Public-site analysis and production access are not the same thing.
AI output is treated as analysis, not authority.
FixRank uses AI to help interpret signals, organize findings, identify patterns, and generate recommendations. AI-generated output can be incomplete, incorrect, or inappropriate for a particular website. Users should review recommendations before relying on them for important technical or business decisions.
Recommendations should be connected to the findings and context that produced them where practical.
AI output should be reviewed rather than treated as automatically correct.
A recommendation cannot guarantee rankings, indexing, traffic, or AI citations.
Analysis should not silently become a production change.
FixRank can prepare recommendations and, where appropriate, deployment-ready fix code. That does not mean FixRank should make unreviewed changes to a live website.
FixRank can surface prioritized findings and prepare fix guidance or code where appropriate. Users remain responsible for reviewing and implementing changes.
Autopilot is intended to support approved execution workflows in a future version of FixRank. Any future deployment capability should be introduced with explicit authorization, scoped access, review controls, and appropriate safeguards.
Autopilot is a roadmap capability — not a current security control.
Customer data should remain scoped to the customer.
Account-specific reports, findings, settings, and analysis should remain associated with the account and website they belong to. The application should enforce authorization boundaries so one user cannot access another user's protected account data through normal product use.
Payments are separated from search analysis.
Where FixRank uses a third-party payment processor for subscriptions, payment processing is handled through that provider's payment infrastructure rather than being mixed with website analysis systems.
Security is shared.
Users also have an important role in protecting their accounts and websites.
- Use a strong and unique password.
- Protect access to the account email address.
- Review recommended changes before deploying them.
- Verify code changes against your own environment.
- Keep website software and dependencies maintained.
- Do not provide unnecessary secrets or credentials.
- Contact FixRank promptly if suspicious account activity is detected.
FixRank analysis does not replace a website owner's own security, testing, backup, or change-management practices.
No online service is risk-free.
No internet-based service can promise absolute security. FixRank works to reduce avoidable risks and improve its safeguards as the platform develops, but users should make their own decisions about whether the service is appropriate for the sensitivity and risk profile of their websites and data.
Found a security issue? Tell us.
If you believe you have discovered a security vulnerability affecting FixRank, please report it privately so the issue can be reviewed responsibly.
Report a Security IssuePlease do not publicly disclose an unreviewed vulnerability before giving us a reasonable opportunity to investigate it.
Security grows with capability.
As FixRank introduces new integrations, automation, and execution capabilities, the security model should evolve with them. Features that require deeper access should introduce proportionate controls rather than inheriting permissions from unrelated parts of the product.
Public-page signals
Findings and guidance
Explicit human review
Scoped, authorized action
Deeper capability requires stronger controls.
Trust starts with saying exactly what the product does.
We will continue updating this page as FixRank's architecture, integrations, and security controls evolve.