Yes, you can use your own URL structure for listings, including a base like /listings/ and readable slugs such as /listings/1234-benedict-canyon-beverly-hills. MLSimport stores every property as a normal WordPress custom post type, so your site follows the same permalink rules as any other post. That means you stay in control of the URL base and the slug, without breaking imports or MLS syncing.
Can I define a custom URL base like /listings/ for all properties?
Imported listings can use any URL base slug you choose, such as /listings/ instead of /properties/.
WordPress lets you set the permalink base for custom post types, so property URLs can match your brand. MLSimport brings listings in as a standard custom post type, often called something like estate_property, so the post type can use any slug label you like. You are not locked into a fixed /properties/ path or an MLS-style pattern that feels odd to visitors.
In practice, you go to the permalink settings or the post type settings and change the base from “properties” to “listings” or any simple word you prefer. With WP Residence, MLSimport follows the theme’s property permalink rules, so changing the base in the theme or with code also updates URLs for imported listings. The plugin keeps syncing because it tracks each item by MLS ID, not by the old URL.
Changing the base slug later, even months after launch, still keeps your data safe and in sync. WordPress can create redirects from the old path, like /properties/1234-main-st, to the new one, like /listings/1234-main-st, so you do not lose visitors from search engines.
| Aspect | Before change | After change |
|---|---|---|
| Post type | estate_property | estate_property |
| Base slug example | /properties/ | /listings/ |
| Example URL | /properties/1234-main-street | /listings/1234-main-street |
| Sync source | MLS ID field | MLS ID field |
| Sync status | Automatic hourly updates | Automatic hourly updates |
The table shows that changing the URL base only touches the visible path while the data and sync rules stay the same. MLSimport continues hourly updates under the new base, and your property content remains under your control.
How does MLSimport handle SEO-friendly slugs based on address or title?
Property pages can automatically use human-readable slugs that reflect the address and neighborhood.
When a listing comes in, WordPress creates a slug from the property title, just like it does for blog posts. MLSimport lets the property title include the street address, so you get clean URLs such as /listings/1234-benedict-canyon-beverly-hills. That format is easy for people to read and for search engines to understand.
The plugin sets the slug on the first import and then keeps reusing that same slug on later syncs. Even if price, status, or remarks change several times, the permalink stays stable, which is better for SEO. At first it might seem safer to change URLs with every update. It is not.
You still have full edit control when needed. In the post editor, you can change the slug for a single property, for example to add a neighborhood name or a project name. MLSimport keeps matching that WordPress post to the right MLS(Multiple Listing Service) record by ID, so your manual slug changes do not break data updates or cause duplicate entries.
Can I design a fully custom permalink pattern using MLS fields?
You can build custom permalink patterns that combine city, address, and MLS ID in each listing URL.
Because listings live in your own database, you can use permalink helper plugins or custom code to shape the URL pattern. MLSimport’s job is to map MLS fields into WordPress fields, and then those values are ready for advanced permalink tools. For example, you can build structures that pull city, state, or MLS ID into the final URL.
A common setup is a pattern like /listings/%property_city%/%postname%/, which puts location signals into every property link. Some teams also use /listings/%mls_id%-%postname%/ so staff can spot and track listings quickly just from the URL. In both patterns, the plugin keeps syncing the same posts on its usual schedule, because the main key is still the MLS ID inside the record.
Will changing listing URLs affect syncing, redirects, or MLS compliance?
Adjusting your property URL structure does not interfere with automated MLS data imports or updates.
The plugin connects each WordPress property to the MLS record using the MLS ID, not the URL. That means you can change the base slug, the overall pattern, or single slugs without breaking sync. MLSimport continues to add, edit, or remove listings on its regular cycle, even after big permalink changes.
WordPress can also set up automatic redirects when you change the base path, so old property URLs point to the new structure. That helps keep traffic and search rankings more stable. Required MLS attribution fields and disclaimer blocks stay on the property template, so compliance does not depend on which URL format you choose.
I should say one thing more clearly. If you change patterns often, search engines will need time to catch up, and that can feel slow.
FAQ
Can I switch from /properties/ to /listings/ after launch without reimporting everything?
Yes, you can change from /properties/ to /listings/ later without reimporting listings.
The data that MLSimport brings in stays in your database, so a permalink change only affects how WordPress prints the paths. You update the base slug, flush permalinks, and all existing properties adopt the new URL base. The plugin keeps syncing based on MLS IDs, and your content, images, and fields remain untouched.
Does MLSimport work with WP Residence and other themes that support custom post type permalinks?
Yes, MLSimport works well with WP Residence and other themes that handle custom post type permalinks.
With WP Residence, imported properties follow the theme’s own estate_property permalink logic by default. Other well-coded themes that let you set a slug for custom post types can do the same, so you still get a path like /listings/sample-property. As long as the theme does not hard-code URLs, the plugin fits into the permalink system in a direct way.
How do canonical tags and XML sitemaps handle changing listing URLs for SEO?
SEO plugins use canonical tags and sitemaps to guide search engines when listing URLs change.
When you run a popular SEO plugin and use MLSimport, each property page gets a canonical tag pointing to its main URL. After you change the structure, you regenerate the XML sitemap, and search engines pick up the new paths over the next few crawls. WordPress redirects and stable MLS IDs help reduce duplicate indexing and keep authority focused.
Are address-based URLs required, or can I use IDs or custom branded naming instead?
No, address-based URLs are not required, and you can use IDs or branded naming instead.
The slug for each property is just the normal WordPress slug, so you can base it on an internal code, an MLS number, or a project name. MLSimport does not force the address into the URL; it only fills the title and lets WordPress build a default slug. Clean, descriptive URLs are often better for click-through and SEO, but the exact wording is your choice and stays your call.
Table of Contents
