Contact Anku AI Tools

Use this page to send feedback, report a tool issue, request a new tool, or discuss partnerships. The fastest way is email so you can include a link and details.

Quick contact

Email supportBrowse all tools

What we can help with

  • Tool bugs: output not generated, UI issues, mobile layout problems.
  • SEO/indexing: page not appearing in Search Console, canonical mismatch, sitemap questions.
  • New tools: tell us the workflow and example inputs/outputs.
  • Partnerships: content, distribution, or integration requests.

Before you send sensitive info

Please don’t include passwords, OTPs, private keys, or confidential documents in messages. For debugging, share a minimal sample input without personal data.

Support and contact guide

Read more

This page explains how to contact Anku AI Tools effectively: what details to include for bug reports, how to request new tools, and how to report indexing issues from Google Search Console. Clear information helps reproduce issues faster and helps keep pages high quality and indexable.

Bug reports: what to include

The fastest bug reports include the exact tool URL and a minimal example that reproduces the issue. Avoid large or sensitive inputs—share a small sample that demonstrates the problem.

If the issue is UI-related (layout, buttons, mobile issues), screenshots help a lot. If the issue is output-related, include what you expected versus what happened.

If you can reproduce the problem across devices (mobile vs desktop), mention that too.

  • Tool URL and tool name
  • Device + browser (for example: Android Chrome, iPhone Safari, Desktop Firefox)
  • Steps to reproduce
  • Expected result vs actual result
  • Screenshot or short screen recording (optional)

Browse all tools

Open any tool page and share its URL in your report.

Privacy Policy

Avoid sharing confidential information.

Requesting a new tool (best format)

If you want a new tool, start by describing the exact workflow you want to complete. A good tool request is similar to a product spec: input → options → output.

Include 1–2 sample inputs and the expected output format (text, JSON, image, PDF, table). This makes it much easier to build a correct UI and to write long-form content and FAQs that match search intent.

If the tool should have multiple modes (basic vs advanced), mention those and list which settings matter for the output.

  • Tool name idea (what should the page be called?)
  • Category (SEO, PDF, image, developer, calculator, converter, business)
  • Inputs (text/file/URL) and expected limits
  • Options (checkboxes, sliders, presets)
  • Output type (copy + download?)
  • Examples (2–3 examples are ideal)

SEO Tools category

See SEO tool patterns (operators, snippets, preview outputs).

Developer Tools category

See format/validate/encode tool patterns.

Indexing issues and Google Search Console

If a page is not appearing in Google Search Console, the first step is verifying the canonical URL, sitemap inclusion, and whether the page returns a valid 200 status with visible content.

Share the exact URL and (if possible) the Search Console message (for example: discovered but not indexed). Then we can expand content, add internal links, or adjust page structure where needed.

Submitting /sitemap.xml to Search Console helps discovery, and tool/category pages are designed to be crawlable through internal linking.

  • Share the exact page URL
  • Share the Search Console status message
  • Confirm the page is in /sitemap.xml
  • Check canonical URL matches the sitemap URL
  • Add internal links from relevant pages if needed

XML sitemap

Submit this in Search Console.

Human sitemap

Browse all indexable pages quickly.

Safety note

Please do not email passwords, OTPs, private keys, or confidential documents. For debugging, share sanitized examples only.

If a tool output is used for legal, medical, financial, or compliance work, always verify outputs before use.

Frequently Asked Questions

What should I include in a support message?

Share the tool name, the page URL, your input (remove sensitive data), what you expected, what happened, and a screenshot if possible. This helps reproduce the issue quickly.

Do you offer custom tools or feature requests?

Yes. You can request new tools, improvements, or category ideas. Include your use case and examples so we can design the best workflow.

Is there a public list of all tools?

Yes. The sitemap page lists categories, tools, and important pages so you can find the right utility fast.

Can I report SEO or indexing issues?

Yes. If a page is missing from Google Search Console, share the URL and we can verify the route, canonical URL, sitemap inclusion, and on-page metadata.

How do I request a new tool?

Send the workflow you want: the inputs, options, the exact output you expect, and 1–2 sample examples. This helps us build the best UI and content for the page.

What is the fastest way to report a bug?

Include the tool URL, your device/browser, the input you used (remove sensitive data), and a screenshot of the result. Clear reproduction steps save time.

Can I suggest SEO improvements to a page?

Yes. Share the page URL and the search query you used. We can expand FAQs, add examples, and improve internal links while keeping the content natural and helpful.

Where can I see all indexable URLs?

Use the sitemap page for a complete list of public pages, categories, and tools.

Do you accept partnerships or sponsored suggestions?

You can contact us for partnerships. We prioritize user value and clear disclosure and avoid low-quality content that hurts indexing.