AI SEO Search Results Explained

When you enable Vehicle AI SEO, your website will be given a page that is structured like the below example. The primary function of this page is to boost your website's visibility in online searches by including keywords, internal links and FAQ sections, all generated automatically for you.

This does make this page act slightly differently from your other website pages, however. The first thing you will notice is that it is vehicle-type specific. e.g. Used CARS For Sale or Used VANS for Sale. This is to better match common terms searched online by potential customers. This is also the reason that, if you stock both vans and cars, they won't both appear on this page.

NOTE: Of course, once you press 'Search', all vehicle types will appear in the search results.


Organise Your Vehicle Types

You can avoid any confusion by splitting the different search pages in the navigation bar.

This will give you separate SEO pages for each vehicle type. As you can see here, there is now an SEO-optimised page for VANS too.

The vehicle types available are determined by what you've ticked in your Website -> Settings -> AI SEO section.


Navigation Header

Start by going to your Website -> Navigation section and edit your current 'Browse Vehicles' or 'Used Stock' page.

Change the URL to 'used' and the Page to '{VEHICLE_SEO_TITLE}'.


Subheadings

In the Add Link section, add a link for each of the vehicle types as a 'Child Of' your Browse Vehicles page ('Used Stock' in this example).

You can copy the two examples below.

Make sure that each link has Page set to {VEHICLE_SEO_TITLE} selected.

The final step is to make sure the URL just says the vehicle type in question, i.e cars or vans.

MUST DO Checklist for links:

  1. Create links as 'Child Of' your Browse Vehicles page, whatever you've named it.
  2. Set 'Page' to {VEHICLE_SEO_TITLE}
  3. Make sure the URL simply reflects the vehicle type - motorbikes, cars, caravans, crossovers, motorhomes, vans etc.

Once you press Save Changes, you should have something that looks like this.


Related Documentation

Usage Guide