Public source requirement
Use public, crawlable source URLs. Do not submit private client files, copied review text, reviewer names, MLS-only screenshots, private financial records, or confidential documents.
Correction Request
Request a factual correction with public source support.
The Index should be useful because it can be corrected. A correction request can fix facts, sources, identity, category, and outdated evidence, but it cannot buy rank movement or favorable placement.
Ranking Boundary
Corrections improve accuracy. They do not move rankings directly.
Correction requests can improve factual accuracy but cannot buy inclusion, rank movement, score changes, badges, referrals, or favorable editorial language.
Review-source requirement
Do not copy review text, rating snippets, or portal profile content unless source terms permit it; use source links and aggregate proof labels instead.
Correction Intake
Submit a source-backed correction.
Use public URLs and factual context only. Do not submit private client files, copied review text, reviewer names, MLS-only screenshots, credentials, financial documents, legal records, or medical records.
Research stageCorrections not open yet
We are not accepting correction requests through this form yet. The Index is currently publishing research, market coverage, and source-backed comparison tools while intake routing is finalized.
Every request is reviewed against the supplied public source. Submission does not change a score, rank, badge, or profile until validation and editorial approval are complete.
Review Process
How correction requests are handled.
- Confirm the correction is tied to a public, crawlable source URL.
- Resolve whether the correction changes identity, market, category, source URL, or score input.
- Check source-rights boundaries and avoid copied review text or reviewer names.
- Queue recompute only if the public source supports a scoring input change.
- Require validation and editorial approval before any public score, rank, badge, or wording changes.
Correction Fields
What a clean correction should include.
| Field | Why it matters | Examples |
|---|---|---|
| Correction typecorrection_type | Classify whether the request concerns identity, category, market, source URL, score input, duplicate cleanup, or outdated evidence. | Identity correction, Market correction, Duplicate/entity cleanup, Outdated source |
| Agent or team namecandidate_name | Identify the public row that should be reviewed. | Example Team, Jane Smith |
| Reported profile URLreported_profile_url | Preserve the exact Index profile that opened the correction form. | https://realestateagentaiindex.com/directory/example-team |
| Team or individualentity_type | Keep individual, team, brokerage, and franchise evidence from being blended. | Team, Individual, Brokerage-level source only |
| Marketmarket | Route the correction to the right market ledger. | Chicago, Los Angeles, New York Metro |
| Public source URLpublic_source_url | Provide a crawlable source that supports the requested correction. | Official profile URL, Brokerage roster URL, Public ranking URL |
| Field to correctfield_to_correct | Name the exact public field or claim that should be reviewed. | Team vs individual, Market, Source URL, Review count, Production source |
| Current public valuecurrent_public_value | Help the research desk find the current claim without guessing. | Listed as a team, Shows Los Angeles, Uses old brokerage profile |
| Requested valuerequested_public_value | State the factual correction supported by the public source. | Individual agent, New York Metro, Updated official profile URL |
| Relationship disclosurerelationship_to_candidate | Separate consumer reports, candidate requests, brokerage requests, and unaffiliated research. | Consumer, Agent/team, Brokerage, Unaffiliated researcher |
| Permission to follow upcontact_permission | Allow clarification without turning the correction into a lead or ranking request. | No follow-up, Follow up about this correction only |