First run
Open the SEO dashboard, sign in with Google, paste a domain or URL, and choose the report language. It is best to start with a public page that loads without a password.
If you are not signed in yet, seodot keeps the entered address and brings you back to the launch after authorization.
- Paste a domain or URL, for example example.com or https://example.com
- Choose the report language: Russian or English
- Choose the result type and start the check
For the first check, use one important page. It makes the report logic easier to understand and act on.
What to choose before launch
The choice shapes the report. You can get a general SEO check, improve copy, prepare title and description, review technical health, build a fix plan, compare pages, or check the visual layer.
SEO check
Best for the first look at a page. The report shows the overall score, copy notes, technical limits, UX observations, and nearest actions.
Copy and structure
Choose it when you need to review copy, headings, answer depth, readability, and fit with user intent.
Title and description
The dashboard creates several title and description pairs from the current page content. It helps rebuild the snippet faster without manually testing every wording.
Technical health
Use it for title, description, indexability, speed, directives, and visible technical limits.
Action plan
Focuses on action: what to do first, what can wait, and which changes should have the clearest effect.
Page comparison
AI finds internal pages and compares them by copy, technical health, and UX. It helps identify which page answers the user need better.
Visual review
Reviews the page screenshot: first-screen clarity, trust, readability, navigation, and visibility of important actions.
Settings before launch
Before starting, you can adjust review conditions. Settings help shape the report around the task instead of returning the same answer for every page.
- Report language controls the output language, not the page language.
- Mobile version gives more weight to phone speed and usability.
- Strict scoring raises important findings higher.
- Visual review adds conclusions based on the page screenshot.
If a page requires sign-in or blocks external requests, the report can be incomplete.
How to read a report
Start with the overall score and the important actions block. Then move through the tabs for issues, recommendations, strengths, and detailed findings.
Below the report you will find the page preview: response status, load time, page size, current title and description, and a screenshot when it is available.
- Start with the important actions block.
- Review content notes together with the current title and description.
- Export the report when you need to share it with a team or contractor.
Title and description
In this result type, the report shows pairs in one column: each title is directly connected to its description. Copy buttons sit next to each line, and the shared keyword list appears below the ideas.
Before publishing, check length, the main query, natural wording, and alignment with the actual page. If a search engine rewrites the snippet, use the next idea as a backup.
Copy title and description separately so you can test several ideas in a CMS or task table faster.
History and saving
History keeps recent checks available so you can return to opened URLs. Saved reports are useful for pages the team revisits often.
Save reports for landing pages, service pages, articles, and other important URLs where quality needs to be tracked after changes.
Compare results
Comparison shows the difference between two runs or several pages. It is useful after edits, redesign work, text changes, or technical updates.
- Compare pages with close goals so the conclusions stay clear.
- After changing a page, run a new review and compare it with the previous report.
- Open a ready comparison from the notification or through the comparison section in the dashboard.
Data access
Google sign-in is required for running reviews, history, and saved reports. Public site pages, FAQ, and documentation remain accessible without sign-in.
Credits and limits
Every launch shows the credit cost before it starts. Free includes 3 credits per day, Pro includes 1,500 credits per month, and PRO+ includes 6,000 credits per month.
A standard URL check costs 1 credit. Comparison, the fix plan, and Cookie scanning cost more because they require more requests and AI work.
A detailed table is available on the Credits and limits page in documentation.
Google Search Console
The Search Console area shows pages, queries, countries, CTR, position, and change compared with the previous period. Access is read-only.
Use these queries in page comparison and title/description updates.
- Connect with the same Google account.
- Choose a site from your Search Console properties.
- AI tips can be launched for individual rows.
Cookie banner
The generator scans a site, finds cookies and services, then provides a text editor and ready JavaScript for installation.
Before publishing, review detected items, document links, and consent copy.
Demo reports
Before the first run, you can view an example SEO report and an example page comparison. They show the result format, action order, and how a report can be shared with a team.
- The example SEO report shows score, important actions, and risks.
- The comparison example shows before-and-after changes.
How to hand off a report
After a review, save the report, copy the short summary, and add the link to the task. A team needs the URL, review date, selected mode, credit cost, and first actions.
If the report goes to a contractor or client, start with the important actions block. The recipient sees what needs to change and which outcome matters.
- Add the URL, review date, and selected seodot mode.
- Copy the first 3-5 actions from the report and assign owners.
- Attach the current title, description, and first-screen screenshot when they matter for the task.
- After edits, run a new review and compare it with the previous report.
For a quick handoff, include the report link, the first three actions, and one note about the number you expect to improve.
Check after edits
A second review helps separate real improvement from a subjective feeling. Compare the page with the same mode and the same report language.
Before changes
Save the original report, current title and description, review date, and the first important findings. This becomes the team baseline.
- Record the score and the first actions from the report.
- Save a first-screen screenshot if UX is changing.
- Mark which page blocks will be updated.
After publishing
Run a new review and compare the score, action list, title, description, technical findings, and first-screen view.
- If the score improves, keep the successful changes in the task notes.
- If new findings appear, separate important items from cosmetic ones.
- After 7-14 days, check impressions, clicks, CTR, and position in Search Console.
Common mistakes
Weak reports usually come from input conditions, not AI: a blocked page, wrong URL, wrong mode, or no clear review goal.
- Reviewing a page that requires sign-in or blocks external requests.
- Comparing pages with different goals, such as an article and a service page.
- Publishing title and description without checking the page meaning.
- Ignoring mobile view when most traffic comes from phones.
- Running several expensive modes in a row without checking the credit cost.
Check the URL, review goal, and credit cost. It saves time and makes the first report more useful.