Let’s talk SEO.
Questions, feedback or need a hand with your reports? Send us a message and we’ll usually get back to you within one business day.
Send us a message
All fields are required.
How to get the right help
SeOMeter supports website owners, SEO professionals, agencies and teams using our audit and research tools. Choose the topic that best matches your request and include enough context for us to reproduce the issue. A useful message includes the page or tool URL, what you expected to happen, what happened instead, and the approximate date and time. If an error is displayed, copy its exact wording. Screenshots can help, but crop or blur personal information that is not needed to resolve the issue.
For a crawl or technical audit, include the target website and the affected report or project reference. Let us know whether the problem happens every time or only on a specific page, and whether it affects one domain or several. Do not include passwords, access tokens, private keys, session cookies or other credentials. If a page requires authentication, describe the steps without sharing your login details.
Billing, plans and account access
For a subscription, renewal, cancellation or refund question, tell us the plan name, transaction date and payment reference where available. Never send a card security code, UPI PIN or one-time password. Review the Refund & Cancellation Policy for the applicable process and the Terms of Service for general service conditions. For sign-in or account recovery problems, use the email address associated with the account and explain the step where access fails.
For feature requests, describe the workflow you are trying to complete and the outcome that would help. We may not be able to implement every request, but specific examples help us assess demand and understand how a change would affect different users and workspaces.
Privacy and security reports
Use the contact form or email support for privacy questions, data correction or deletion requests, suspected security vulnerabilities, and reports of exposed information. Tell us which feature or URL is involved and the potential impact. Do not send another person's private data or attempt to access an account, domain or workspace without permission. For a suspected vulnerability, provide a concise description and safe reproduction steps; avoid destructive testing or accessing data that is not yours.
We may ask for reasonable verification before making account changes or sharing account-specific information. This protects users against impersonation and unauthorized disclosure. Read the Privacy Policy for information handling and the Data Safety & Security page for security practices and limitations. Formal complaints can be sent to our Grievance Officer.
Grievance Redressal
Grievance Officer: Alok Chaurasia, Rajendra Nagar, Gorakhpur, Uttar Pradesh, India. Email: support@seometer.in (subject line “Grievance”). From 1 January 2027, where the Consumer Protection (E-Commerce) (Amendment) Rules, 2026 apply, we will also provide the complainant a copy of the complaint as recorded by the Grievance Officer. We acknowledge complaints within 48 hours of receipt and aim to resolve them within 30 days.
What happens after you contact us?
We use the information you submit to understand and respond to your request. We may reply with troubleshooting steps, ask a follow-up question, or route the message to the team responsible for the relevant feature. Please check your inbox and spam folder for replies. Response times can vary during weekends, holidays or periods of unusually high request volume; urgent security reports should be clearly marked in the subject line when sent by email.
Submitting a message does not guarantee a particular product change, audit outcome, refund or legal result. Any billing or data request is assessed under the applicable policy and law. For general questions, the fastest route is usually to describe one problem per message and include the exact URL. This helps keep the exchange clear and avoids sending information that is not needed.