Use the right inbox so your message gets handled properly.
We treat corrections, editorial questions, and business requests differently. Sending a clear message to the right place makes the response faster and more useful.
A clear message is faster than a broad complaint.
Corrections, sourcing questions, and business requests should land in different lanes. The contact page is meant to reduce ambiguity before the email is ever sent.
Pick the inbox that matches the type of issue instead of sending everything to one mailbox.
Include the page URL, section, and the expected fix or question.
Use the process pages when the issue is really about policy rather than one article.
Email is the cleanest support path for the current site. Use the contact route below that matches your issue so requests land in the right workflow from the start.
If you are reporting a factual concern, include the article URL, the specific claim or section, and any source you think should be reviewed.
Choose the lane that matches your request.
Sources, claims, and page quality
Use this for article feedback, evidence questions, citation issues, or requests for clarification on health content.
Report a factual or linking issue
Send the page URL, the section in question, and a short explanation of what looks inaccurate or broken.
Partnerships or operational requests
Use this for partnership inquiries, licensing questions, or operational matters that are not editorial corrections.
The fastest messages to resolve are the most specific ones.
- +Include the exact page URL or route.
- +Name the section, paragraph, or CTA that caused the issue.
- +If the problem is factual, include the source you want reviewed.
- +If the problem is technical, note device type, browser, and what you expected to happen.
What to expect after you email us.
We prioritize corrections, broken links, and issues that affect reader safety or page accuracy. General suggestions and partnership outreach are reviewed after urgent content problems.
Not every message will result in a public change, but specific correction requests are reviewed as editorial tasks rather than ignored as generic feedback.
Sometimes the fastest answer is already documented.
Before sending a message, check the process page that matches the issue. That cuts down on unnecessary back-and-forth and keeps policy questions out of the general inbox.
Editorial policy
Use this when your question is really about how claims, sources, or product language are handled.
Corrections policy
Use this when you need the documented workflow for factual updates, broken links, or public corrections.
Medical disclaimer
Use this when the issue is about the limits of site content versus diagnosis, treatment, or emergency care.
Want context before you write?
Read how the site works and how pages are reviewed before sending a correction or sourcing question.