Run your first website audit
Start your first LLMIC website audit, choose a crawl source, confirm scope and review the resulting pages and issues.
Your first website audit should be small enough to understand and representative enough to reveal useful issues. Start with a website you own or are authorized to assess. LLMIC can work from a website URL, sitemap or URL list. These sources define different starting points, so record which one you used before comparing results with a later crawl.
What this guide helps you do
A website audit for SEO should begin with a controlled crawl and end with evidence you can review. This walkthrough shows how to choose a source, run the first LLMIC audit and interpret the initial completion state.
Choose a starting point
Open the crawl controls and select the source that matches your task. A website URL is useful for exploring linked pages. A sitemap starts with the URLs declared in that file. A URL list is useful when you already know the exact pages to inspect. Check the domain and source before running so a previous project or placeholder does not define the wrong scope.
Review settings before running
Review the available crawling and rendering settings in Settings. Choose settings appropriate for your website and plan limit rather than assuming every page needs the same rendering method. JavaScript-heavy pages can expose different information after rendering than in the original response. If a site needs authentication or blocks requests, resolve the access requirement before expecting a complete content audit.
Start and watch progress
Start the audit from the crawl bar. Watch the discovered or processed page counts and any failure indicators. While work is running, treat results as incomplete. A partial crawl is not a reliable baseline for a finished crawl, especially when different sections have been discovered. Keep the Mac available during local work and avoid changing the source simply to interpret the current results.
Inspect a few pages first
When the audit finishes, open Pages and inspect a small sample: the homepage, an important content page and a page with a reported issue. Confirm the URLs and response evidence belong to the site you intended to crawl. Then open Issues to inspect affected pages and recommendations. A count tells you how many observations match a condition; it does not explain every individual cause.
Choose your next action
Prioritize findings with clear evidence and meaningful impact on important pages. Use Queue to organize selected tasks instead of rewriting everything at once. Save an export where useful and record the crawl scope before making changes. After implementation, run a comparable follow-up audit. Missing data, failed access and unsupported checks should remain investigation items rather than being interpreted as proof that a problem is absent.
Quick reference
| Source | Good starting use |
|---|---|
| Website URL | Explore a linked website |
| Sitemap | Inspect declared sitemap URLs |
| URL list | Check a known group of pages |
| Follow-up crawl | Compare equivalent scope after changes |
Continue learning
Next, understand audit results, organize and prepare fixes. Return to the documentation home to explore other guides. If the result differs from these instructions, contact support with your app version and the relevant steps. Remove private information from screenshots and never include API keys or passwords.
Frequently asked questions
Start your first LLMIC website audit, choose a crawl source, confirm scope and review the resulting pages and issues.
Load a completed crawl that includes the pages you need to inspect. Confirm the crawl scope, capture time, rendering choice, and any filters before interpreting the result.
Review the affected URL, measured field, source or rendered evidence, and the rule that raised the item. Inspect nearby pages and templates because one shared component can create the same pattern across many URLs.
Create a task with the affected URL, observed evidence, intended outcome, smallest safe change, owner, and verification method. Keep the measured finding separate from the proposed fix.
Publish the approved change, run a fresh compatible crawl, and compare the new evidence with the saved result. A resolved local finding confirms the implementation changed; search performance requires separate observation over time.
The check cannot guarantee rankings, indexing, traffic, conversions, inclusion in an AI answer, or a future search-engine action. Interpret it with site context, search performance, and editorial judgment.
Save or export the evidence, assign the approved action, and use the related guides linked on the page for the next check. After implementation, repeat the same workflow against a fresh crawl so the result is comparable.