Contact
Questions, feedback, or suggestions? We’d love to hear from you.
Email us at: everydayroyalties@gmail.com
We typically respond within 1–3 business days.
How to reach us
We want this tool to stay fast, accurate, and genuinely helpful. If you reach out, include the page you were on and (if relevant) a short sample of the text that caused the issue.
Bug reports
Found a counting edge case, broken layout, or export problem? Tell us what happened and what browser/device you’re using.
Content feedback
Want a new article topic or a clearer explanation of metrics? Suggest it—editorial improvements are welcome.
Partnerships
If you’re an editor, educator, or product team that wants to collaborate, share what you’re building and how this tool could help.
Response time
We typically respond within a few business days. During high volume, it may take a bit longer.
Frequently asked questions
Can you add a feature?
Yes—feature requests are welcome. The most helpful requests include a short “why” and an example workflow.
I found a typo in an article.
Send the article title and the sentence. We’ll fix it quickly.
Do you offer support for teams?
If you need a custom workflow (bulk checks, exports, or style constraints), contact us with your use case.
How to Get the Fastest Support
If you’re reporting a bug, include the browser you’re using (Chrome/Safari/Firefox), what you pasted (a short sample is fine), and what you expected to happen.
If something looks ‘off’ in the results, tell us whether you used copy/paste from a webpage (those can include hidden characters).
- Bug reports: include steps to reproduce.
- Feature requests: describe your workflow and what you’re trying to accomplish.
- Partnerships: include your site or product link and the collaboration idea.
Common Fixes (Before You Email)
If the tool seems slow, try analyzing smaller chunks of text first and then the full document.
If your results include strange symbols, try pasting into a plain-text editor first to remove formatting.
- Hard refresh the page and try again.
- Try a different browser to compare behavior.
- Disable aggressive extensions that modify page content.
If You’re Reporting a Bug, Include
Clear details help us reproduce the issue quickly. Please avoid sending private information—short samples are enough.
- Browser and device (e.g., Chrome on Mac).
- Steps to reproduce (what you clicked).
- What you expected vs what happened.
- Screenshot if it’s a visual glitch.
What Happens After You Email Us
After you email, we’ll review your message and respond with next steps. If it’s a bug, we may ask for a short sample or screenshot to reproduce it.
If it’s a feature request, we’ll confirm the use case and consider it for future updates.
- Support requests: include browser + steps to reproduce.
- Feature requests: describe the workflow and expected output.
- Partnerships: include context and a clear proposal.
Examples of Messages We Can Act On
Good messages are specific. Here are examples that help us respond fast without needing follow‑up questions.
- “On Chrome, the table doesn’t sort when I click the header. Here are the steps I took…”
- “My readability score seems wrong on this paragraph. Here’s a short sample and what I expected…”
- “Can you add an export that includes word, count, and percentage? My use case is…”
Tips for Faster Resolution
When you include the right details, most issues can be solved quickly. If the issue is visual, screenshots help. If it’s accuracy-related, a short sample helps.
We’ll never need your private info to troubleshoot a sorting or formatting issue.
- Include browser + device.
- Include steps to reproduce.
- Include expected vs actual result.
- Include a screenshot when relevant.
Partnership and Feedback Ideas
If you want to collaborate, the most helpful message includes context, what you propose, and what success looks like. We’re especially interested in partnerships that help writers and site owners improve clarity.
Feedback is welcome—tell us what task you were trying to complete and what would have made it easier.
- Include your website or product link.
- Describe the audience and workflow.
- Suggest the feature or collaboration in one paragraph.
What to Send for Content Feedback Requests
If you’re asking for feedback on a page, include your goal and the audience. ‘Make it better’ is vague; ‘make it clearer for first-time readers’ is actionable.
You can also include your top 3 questions you want the page to answer—those often become the best headings.
- Goal (SEO clarity, readability, uniqueness, etc.).
- Audience (beginners, technical users, students).
- Top 3 questions the page should answer.
- Any constraints (must keep terms, tone, or structure).
What to Send for Feature Requests
The best feature requests describe a real workflow: what you’re trying to do, what output you need, and why current options don’t solve it.
If possible, include a rough example of the export or screen you want.
- State the goal and who it’s for.
- Describe the steps you currently take.
- Describe the desired output (fields, format).
- Include a small example if relevant.
Common Topics We Get Questions About
Most questions fall into a few categories. If you include which category you’re in, we can respond faster.
- Accuracy questions: why a word count looks high or low.
- Formatting issues: pasted text has strange characters.
- Feature requests: exports, filters, stop-word controls.
- Partnerships: content collaboration and tool ideas.
Privacy and Security Reminder
For security, do not email sensitive personal information. If you need to demonstrate an issue, use a short, anonymized sample.
This helps us troubleshoot while keeping your data safe.
- Remove names/emails from samples.
- Use short excerpts.
- Never send account numbers.