New: Operator, the chat that answers questions about your site
RankMySEO home
Start for free
All skills
Launch

Check a new site's first weeks after launch

In the first week, confirm the basics work. In the first month, confirm the numbers are arriving. Your assistant sorts the site into one of three states and gives one fix for each broken item.

Send feedbackConnect RankMySEO

Example

You ask

We launched the new site last week. Can you check that Google can read it and tell me what to fix first?

The assistant

Your assistant opens the homepage, sitemap, and robots file, then reads the first Search Console rows. Few rows in week one is normal, so it reports the site as waiting, names each broken item with one fix, and sets a date to check again.

Use it when

  • The site went live in the last month.
  • A redesign, a domain move, or a template change is coming, or has just shipped.
  • You ask why the new site shows no search traffic yet.

You give it

  • The live site address, plus one key service page to check.
  • Search Console and GA4 access, read directly or through RankMySEO.
  • A RankMySEO account, if you track keyword ranks. Without one, the rank steps are skipped.
  • For a move or redesign, the old and new URLs, so the redirect map can be checked.

It returns

  • A status for each check: homepage, sitemap, robots file, schema, and accessibility.
  • One of three states for the site: crawling and indexing, waiting, or broken.
  • One named fix for each broken item, in priority order.
  • For a release, a before and after comparison that flags anything that changed, when you saved a snapshot before the release.

How the skill runs

  1. Check the homepage and a service page

    Open the live homepage and one service page. Check the title, description, H1, and canonical link, and confirm the URL form matches the sitemap.

  2. Check the sitemap and robots file

    Open /sitemap.xml and /robots.txt. The sitemap should load and list canonical URLs, and the robots file should list it. Indexing requests follow seo-indexing.

  3. Check AI access and schema

    Confirm the Search generative AI control in Search Console includes the site. Run an agent-readiness scan on the homepage, then validate schema on the live URLs until it reports zero errors.

  4. Check that every control has a name

    Check the accessibility tree on the homepage and one service page. Every button, link, and form field needs a name, since a missing name blocks assistive technology and browser agents.

  5. Read the first 28 days of data

    Read the last 28 days of Search Console. Few rows in the first days is normal. Check that the homepage appears in the GA4 pages report, and check the GA4 tag first if no pages appear.

  6. Read tracked keywords and issues

    New keywords show an empty position until the next rank check, which is normal. Once an audit has run, give the top three issues by pages affected, and compare Search Console with tracked rank.

  7. Sort the site and set a check date

    Place the site in one state: crawling and indexing, waiting, or broken. For each broken item, name one fix. Make the change in the builder only if you ask, and set the next check date.

Where it stops

  • Steps that read tracked keyword rank need RankMySEO. Without it, your assistant skips them and says so.
  • Your assistant changes the builder only when you ask, and asks you before it changes the Search generative AI setting.
  • No plan can guarantee a ranking. Early numbers are small, and one spike does not make a trend.

Questions before you install

Do I need RankMySEO to use this check?

No. Steps that read tracked keyword rank need RankMySEO. Without it, your assistant skips those steps and says so. Search Console and GA4 can be read directly.

How long before a new site shows search traffic?

New sites often take weeks to show search traffic, and some get none for a while. Early numbers are small, so the check sets a date to look again.

Does this cover a redesign or a domain move?

Yes. Before a release, your assistant records the status code, title, canonical, robots tags, and JSON-LD types for your most-clicked and money pages. After it, the same pages are compared, and anything that broke is fixed before you request indexing. A domain move also needs a Change of Address in Search Console, and redirects kept for at least a year.

Other skills