Use the right contact path for feedback, bugs, and improvements

Best way to report an issue

The clearest way to report a problem is to include the affected page URL, a short description of what you expected, what happened instead, and the browser or device you used. If the issue is visual, a screenshot is very helpful. If the issue is SEO-related, include the exact page URL and the behavior you noticed in Google Search, Search Console, or social previews.

For code, tool behavior, and site issues, the primary public feedback path is the project repository: GitHub repository. That is the best place for reproducible fixes, improvement requests, and tool suggestions.

What to include in your message

• The page URL, such as /sql-formatter/ or /regex-tester/.
• Whether the problem is a bug, content issue, SEO issue, or feature request.
• Steps to reproduce the issue.
• Example input and output if the problem is tool-specific.
• A screenshot if the issue involves layout, search appearance, or mobile rendering.

SEO and indexing feedback

If you notice title issues, duplicate descriptions, missing snippets, favicon problems, or Google indexing gaps, include the page URL and where you saw the issue. That makes it much easier to fix metadata, sitemap entries, internal links, structured data, or search-preview details.

Pages that commonly benefit from this kind of review include the SQL Formatter, Regex Tester, Timestamp Converter, and Hash Generator pages, along with the related guide pages under /guides/.

What this contact page is for

This page is not a live support desk, but it gives visitors and search engines a clear contact route and establishes that the site has a maintained feedback path.