# SEO Conflicts
# Description
SEO conflicts occur when there is a problem with the output of the SEO generator that causes issues when translating SEO URLs and queries.
For example, if an SEO-friendly URL had the value Berserk/1990, is that 1990 the year it was first written or the volume number? This is what causes an SEO conflict.
# Conflict Resolution
Most of the time the SEO generator will detect any kind of conflicts that may occur once the generator is run. The generator will detect these conflicts and avoid them by not translating them and leaving them as non-SEO friendly when generating so the translator doesn't pick up on them and cause errors.
# Tagging
Tagging involves providing the generator with a "tag" to place after the SEO-generated value in order to not cause confusion and completely avoid any conflicts that may occur due to similar naming as now each value has a tag associated with it that defines which index it belongs to. e.g. Manga-genre where manga is the genre of book.
# Priority Conflict Resolution
A "king" is selected based on a setup priority which takes the highest priority when running the SEO generator. meaning that if conflicts occur between the king and other SEO values, it will select the king and ignore all the others.
# Setting up a Priority
In order to set up a priority system for the SEO generator, there is a section named "PriorityOrderConflict" within the SEO configuration that creates a priority system based on the order of the aspects within the list. Items further up the array of aspects are a higher priority with the first item being the highest priority.
# Example
"PriorityOrderOnConflict": [
"Genre",
"Series"
],
Those that are in conflict means that no SEO-friendly URL will be generated for them and they will be left as regular queries.
# RuleBasedFormatterOptions
This is a section within the config files that lets you determine how you distinguish between SEO values. The main section of this is the default formatting rule which will be used if the specified aspect, range, or POI do not have any custom formatting rules.
# Example
"RuleBasedFormatterOptions": {
"DefaultFacetFormattingRule": {
"Format": "(value)"
},
"FacetFormattingRules": {
"Genre": {
"Format": "(value)-genre"
}
}
},
This example is using the Aspect as the type we are formatting, but the word facet can be changed to range or POI if desired for example, "RangeFormattingRules" and "DefaultRangeFormattingRule"
within the FacetFormattingRules the aspect "Genre" has rules where every genre facet will be labeled with (value)-genre e.g. Fantasy-genre. This avoids SEO generator conflicts as now the translator can distinguish between genre SEO values and other kinds of facet SEO values that may have the same value.
# Choosing when to accept a conflict
SEO is all about making sure that the search engine you're using can see the entire website and bump it up in the rankings when searching. The SEO-friendly URLs are a way of doing this as well as including many links inside the pages. However, sometimes you may have to decide whether or not it is worth the hassle to resolve a conflict and make it SEO friendly. If there is enough detail about the page that makes it SEO friendly it may be better to just leave it to save time fixing it as the search engines will still be able to crawl through your website using the currently generated URLs.
