Found a false positive?
Tell us.
Every rule has documented exceptions, if the free SEO tool flagged something incorrectly, reporting it improves the engine for everyone.
What to include
- The audited URL and the issue ID (e.g. TITLE-DUP)
- Why you believe it is a false positive
- A screenshot of the rendered page if relevant
Direct line
Reach out via janakpokharel.com.np/contact, the same person who builds the tool reads every message.
Send a report
Fill this in, press send, and your email app opens with everything pre-written, or copy the text and send it however you like.
What happens next
Confirmed bugs become new test fixtures so the same mistake can never ship twice. Good suggestions join the public roadmap. Either way you get a reply, a free tool only stays sharp if its users keep it honest.
Prefer to debug it yourself?
Run the free SEO check again after your fix and watch the issue disappear from the report. Each finding links to a glossary page explaining the rule in plain words, with the official documentation it came from.
Bugs, questions, ideas
Use one message per topic so each can be tracked separately. For bugs, paste the audited URL and the issue ID exactly as shown in your report. For ideas, describe the job you were trying to do, the best features come from real workflows, not wish lists.
Response time
Messages are read in the order they arrive, usually within a few days. Reports with a URL and an issue ID get answered fastest, because the problem can be reproduced immediately instead of going back and forth.
How to write a report we can act on
The most useful reports contain four things: the exact address you audited, the finding or issue ID, what you expected to see and what you saw instead. If the problem is visible in a browser, a short description of the steps to reproduce it saves a lot of time. If a tool on the free tools page misbehaves, tell us which tool, which browser and which device you used, and paste the input that caused the problem if it is not private.
Questions we can help with
- Understanding a finding. If the explanation on the glossary page is unclear, tell us which part, and we will rewrite it.
- Disagreeing with a finding. Some rules have exceptions. Explain why your page is fine and we will check whether the rule needs more context.
- Feature ideas. Describe the job you want to do and why the current tools fall short.
- Corrections to guides. If you spot an out of date or incorrect statement, send the page and a link to the source.
- Accessibility problems. If something on this site is hard to use with a keyboard, a screen reader or a small screen, we want to know.
Security reports
If you believe you have found a security problem in the site or the audit API, please send the details privately through the direct line above rather than posting publicly. Include the steps to reproduce and the potential impact. A security contact file is also published at /.well-known/security.txt.
What we cannot do
We cannot offer individual SEO consulting through this form, review private sites that need a login, or guarantee a particular ranking. We also cannot recover or edit your website. If you need hands-on help, the audit results and fix prompts give you a clear brief to hand to a developer or an agency.
Tips before you write
Run the audit again to confirm the finding is still there, since sites change. Check the glossary entry for the finding to see whether your case is already explained. Look at the official source linked in the finding. These three steps answer many questions immediately and make the ones that remain much easier to resolve.
Common questions before you write
Do you offer SEO consulting?
Not through this site. The audit is designed to give you a clear list of fixes you can do yourself or hand to a developer.
Can you remove my site from the audit cache?
Results are cached for about an hour and then discarded automatically. You can also block the audit bot in robots.txt.
Can I suggest a new free tool?
Yes. Describe the job you want to do, how you do it today and where it is slow or painful.
Do you accept guest posts or sponsored content?
At present we do not publish third party articles. If that changes, it will be announced on this site.
Response times
Messages are read in the order they arrive. Bug reports with a page address and a finding identifier are usually answered first because they can be reproduced straight away. Please allow several days for a reply, and send a second message only if something important has changed.
Example of a good false-positive report
"I audited https://example.com/shoes and got TITLE-DUP for two pages. The pages are /shoes and /shoes?page=2, which are paginated listings and have a canonical pointing to the first page. I think the rule should ignore pages whose canonical points elsewhere. Screenshot of the source attached."
That report names the page, the finding, the reason and a suggestion, so it can be reproduced and checked in minutes. Compare it with "the tool is wrong", which would need several rounds of questions before anyone could look into it. The more specific you are, the faster the fix.
What happens to your message
Your message is read by a person and used only to answer you and to improve the tool. We do not add you to any mailing list and we do not share your details. If you send a screenshot or a page address, we may use it internally to build a test case, and we will not publish it with your name or site attached without asking you first.
Other ways to help
Tell a colleague about a tool that saved you time, link to a guide that helped you, or share a mistake you spotted in a result. Small contributions like these keep a free tool accurate and visible without any paid promotion.
Language and accessibility
Messages in English are answered fastest, though plain descriptions in other languages are welcome and we will do our best to understand them. If you need information in another format, such as plain text or larger type, tell us what would help and we will try to provide it.
A note on spam and sales messages
We receive many unsolicited offers for link building, guest posts and paid placements. We do not buy or sell links and will not reply to these messages. Genuine questions about the tools, bugs and ideas are always welcome and always read.
Keeping the conversation useful
Please keep each message to one topic, so that every question or report can be tracked and answered separately. If you have several findings, send them as separate messages or as a clear numbered list. When we reply, we may ask for one extra detail, such as the browser you used or the exact text of a finding, so please watch for it. A short, friendly exchange almost always solves the problem fastest.