Site Settings

The Site Settings section covers the basic information for your site, such as its name, language, theme and SEO options. Each set of options is divided into a separate block to make it easy to distinguish between groups of settings. This section will look at each block, and the options inside them, starting with:

Basic Settings

The first block covers the most basic options required for your site; some are set when creating your site, while others can be adjusted here. The available options are:

Site Avatar - By clicking on an icon and color, you can customize your site's avatar. This avatar is used only in the Publii backend; it will not be seen on the live website.
Interface colour - Choose the colour used in Publii when working on this site. This affects the app interface only; it does not change the live website.
Site Name - Set the name for your site. This is used in the Publii backend and can appear in your website's text logo and page titles, depending on your theme and SEO settings.
Site Description (Internal) - Add an internal description for your site. This description is for internal use only and will appear in the site selection list within the Publii backend.
Language - Set the language of your site, including its HTML lang attribute and localized dates. Choose Custom to enter a language code manually. Theme text is translated separately using a language file; see the Translate Theme section of this guide for more information.
Enable Spellchecker - Publii includes a spellchecker (OS spellchecker for macOS and Hunspell on Windows and Linux) to help you catch errors as you write; when enabled, unknown words or acronyms will be underlined in red. Right-click on a word to see alternative spelling suggestions for the word. Toggle this option off to disable the spellchecker. On Windows and Linux the spell checker language is set based on the language of the site (see above), on macOS it follows the system spellchecker settings. Not every site language has a supported spellchecking dictionary.
Current Theme - Sets the current theme for your site. Themes installed via App Settings > Themes will appear here. When a newer version is installed in your theme library, use the update option beside the current theme to apply it to this site, then save your settings. Available marketplace updates may also include a download link and an option to install the downloaded theme file.

Advanced Options

Content is a big part of a website's success, but there are plenty of other areas that deserve attention. Publii includes advanced options covering SEO, social media, privacy, image processing and feeds. To reach these options, click on the Site Settings option in the left-sidebar, then scroll down to the Advanced Options group. Its settings are organized into tabs.

Let's look at the options in this section one-by-one.

SEO

SEO (Search Engine Optimization) helps search engines understand your website. The options here control metadata and indexing instructions for different types of pages.

Noindex Website - Adds site-wide indexing restrictions and, when Publii generates your robots.txt, a rule disallowing crawling. This discourages search engines from listing your website, but does not make it private or reliably remove URLs already indexed. Several individual SEO controls are hidden while this option is enabled.
Block GPTBot Bot - Adds a robots.txt rule disallowing GPTBot, OpenAI's crawler for content that may be used to train its models. This option applies only when you do not use your own robots.txt file.
Block ChatGPT-User Bot - Adds a robots.txt rule for ChatGPT-User, which visits pages in response to user actions. OpenAI notes that these requests may not follow robots.txt, so this setting cannot guarantee that visits are blocked. It applies only when you do not use your own robots.txt file.
Block Common Crawl Bots - Adds a robots.txt rule disallowing Common Crawl's CCBot. This option applies only when you do not use your own robots.txt file.

Managing crawler rules with robots.txt

When you enable the bot options above, Publii adds the corresponding rules to its generated robots.txt file. For example, enabling all three options adds:

User-agent: ChatGPT-User
Disallow: /
User-agent: GPTBot
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: *
Disallow:

These rules depend on crawlers respecting them; they are not access controls. Blocking GPTBot also does not block OpenAI's separate search crawler, OAI-SearchBot. See OpenAI's crawler documentation for the differences between these agents.

Creating a Custom robots.txt File

In scenarios requiring more tailored control over your site's indexing and bot interactions, Publii allows for creating a custom robots.txt file. This can be accomplished by generating a robots.txt file in the File Manager at the site's root directory. Opting for a custom robots.txt means that Publii will use this file over the automatically generated one, allowing you to supply your own crawler rules.

Note: It's important to remember that with a custom robots.txt file, you are responsible for manually including any necessary rules to manage bot access. The automatic settings provided by Publii's interface will not apply, so include the rules and sitemap reference you want crawlers to use.

Homepage and posts index

The options shown here depend on whether your homepage displays a page or a list of posts, and whether you have set a Post Prefix in the URLs tab.

Set page as homepage - Allows you to choose a page as the homepage of your website. Your theme must support pages. The selected page's SEO settings then control the homepage metadata.
Posts index - With a post prefix such as blog, your posts index is available at https://example.com/blog/ and has its own SEO settings. Without a prefix, the post listing normally occupies the homepage. If you select a page as the homepage and leave the prefix empty, the separate posts index and its pagination are not generated.
Homepage - Separate homepage SEO fields appear when a post prefix is set and no page is selected as the homepage. This lets you give the homepage and posts index different metadata.

The available metadata and pagination options are:

Page Title - Sets the title used in the browser tab and as a possible source for the title shown in search results.
Meta Description - Provides a short description that search engines may use in search results. They may also choose text from the page itself.
Meta Robots - Sets indexing and link-following instructions for search engines. The same choices are used in several other SEO sections:
- index, follow - Allows indexing and following links; this is the default behaviour.
- index, nofollow - Allows indexing while asking crawlers not to follow links on the page.
- index, follow, noarchive - Adds the legacy noarchive directive to index, follow.
- index, nofollow, noarchive - Adds the legacy noarchive directive to index, nofollow.
- noindex, follow - Requests that the page be excluded from search results while allowing links to be followed.
- noindex, nofollow - Requests that the page be excluded from search results and its links not be followed.
Disable Homepage Pagination Indexing - Excludes additional posts-index pagination pages from the sitemap and adds noindex, follow to them. The pages remain available to visitors.
Disable Homepage Pagination - Stops Publii from generating additional pagination pages for the posts index.

Note: Search engines choose how to display titles and descriptions. Meta robots rules do not restrict access to a page, and crawlers must be able to read a page to see its noindex instruction. Google no longer uses noarchive; see its robots meta tag documentation.

Post Page

Page Title - As with the Page Title for the homepage, this provides search engines with a default title for individual posts. You can use %posttitle, %sitename and %authorname, or override the title in an individual post's SEO settings.
Meta Description - Just like the Meta Description for the homepage, this provides information about the content of your post pages for use in searches and search results.
Hide custom excerpts on post pages - If this option is enabled your post pages won't display text which is placed above the "Read more" element in the post editor.

Tags List Page

Page Title - As with the Page Title for the homepage, this provides search engines with a title for your tags page to be displayed in search results.
Meta Description - Just like the Meta Description for the homepage, this provides information about the content of your tags page for use in searches and search results.
Meta Robots - Sets whether the tags list page is indexed and links followed by search engines.

Note: The Tags Page is only available if your theme supports it. Otherwise, the settings for this page will not be available.

Tag Page

Page Title - As with the Page Title for the homepage, this provides search engines with a title for your tag listing page to be displayed in search results.
Meta Description - Just like the Meta Description for the homepage, this provides information about the content of your tag pages for use in searches and search results.
Meta Robots - Sets whether tag pages are indexed and links followed by search engines.
Display Tags w/o Posts - If enabled, any tags that do not have any posts assigned to them will still have their subpages created and will appear on the tag list on the website.
Disable Tags Pagination Indexing - Excludes tag pagination pages from the sitemap and adds noindex, follow to them.
Disable Tags Pagination - If toggled on, pagination files will not be generated at all.

Author Page

Page Title - As with the Page Title for the homepage, this provides search engines with a title for your author page to be displayed in search results.
Meta Description - Just like the Meta Description for the homepage, this provides information about the content of your author pages for use in searches and search results.
Meta Robots - Sets whether the author page is indexed and links followed by search engines.
Display Authors w/o Posts - When this option is enabled authors created on your site that do not have any posts yet will still have subpages generated for them and will appear on the list of site authors.
Disable Authors Pagination Indexing - Excludes author pagination pages from the sitemap and adds noindex, follow to them.
Disable Authors Pagination - If toggled on, pagination files will not be generated at all.

Use author website in structured data - When enabled and an author's Website field is filled in, Publii uses that address as the author URL in JSON-LD structured data instead of the site's author-page URL.

Error Page

Page Title - As with the Page Title for the homepage, this provides search engines with a title for your error page to be displayed in search results.
Meta Description - Just like the Meta Description for the homepage, this provides information about the content of your error page for use in searches and search results.
Meta Robots - Sets indexing and link-following instructions for the error page; see the homepage Meta Robots option above for more information.

Search Page

Page Title - As with the Page Title for the homepage, this provides search engines with a title for your search page to be displayed in search results.
Meta Description - Just like the Meta Description for the homepage, this provides information about the content of your search page for use in searches and search results.
Meta Robots - Sets how search engine robots should treat your search page; whether it should be indexed and its links followed.

Note: Tag, author, error and search page settings depend on your theme supporting those page types. Unavailable options are disabled or accompanied by an explanation in Publii.

URLs

URLs are the addresses used to visit your website, and Publii includes options to fine-tune the appearance and hierarchy of your URLs.

Use pretty URLs - Uses addresses such as https://example.com/post/ instead of https://example.com/post.html. Pretty URLs also allow page hierarchy to appear in page URLs. This option is enabled by default for newly created websites in Publii 0.48.0; updating Publii does not change the setting for existing sites.
Always add index.html in URLs - Use this option if your server cannot load index.html automatically when a directory is opened.
Post Prefix - Adds a prefix before post slugs, for example https://example.com/blog/post-slug/. The posts index is then available at https://example.com/blog/, with pagination under https://example.com/blog/page/2/. This is useful when a page is set as your homepage and you want to keep a separate blog. This option requires Use pretty URLs.
Tag Prefix - Text entered here appears before the tag slug, for example https://example.com/tags/tag-slug/.
Put tag prefix after post prefix - When enabled, the post prefix is also included in tag URLs, for example https://example.com/blog/tags/tag-slug/. This option appears when a post prefix is set.
Author Prefix - Text entered here appears before the author slug, for example https://example.com/authors/author-slug/.
Put author prefix after post prefix - When enabled, the post prefix is also included in author URLs, for example https://example.com/blog/authors/author-slug/. This option appears when a post prefix is set.
Pagination Phrase - Text entered here appears before page numbers when browsing the second or later pages of post listings, for example https://example.com/page/2/.
Error Page - Defines the filename of your error page. Defaults to 404.html.
Search Page - Defines the filename of your search page. Defaults to search.html.

Note: Changing URL settings on an existing live website can change published addresses. Set up redirects from the old URLs when needed.

Publii URL settings with pretty URLs enabled, a blog post prefix and separate controls for tag and author prefixes. — Use a post prefix to keep your blog under a separate address, and choose whether tag and author URLs should include it.

Sitemap

An XML sitemap lists URLs on your website to help search engines discover your content. Publii can generate it automatically. The options in this section are:

Create XML Sitemap - Ticking this will allow Publii to create a sitemap for your website.
Sitemap Content - Here you can decide which parts of your site you want included in the sitemap, with toggles covering Tag Pages, Author Pages, Homepage Pagination, and External Images. Enable or disable each section that applies as needed.
Excluded Files - If you wish to exclude specific files or folders from the sitemap, enter a comma-separated list, for example avoid-this-file.html,avoid-this-folder.

Note: Sitemap generation is unavailable when Noindex Website is enabled or when Use relative URLs is enabled in Server Settings.

Open Graph

Despite the rather technical name, Open Graph Tags are simply a way to customize how your articles or page links will look like when shared on social networks like Facebook. They provide a title, description and image for shared links. The options in this section are:

Generate Open Graph tags - Set whether Open Graph tags are generated or not; generally, you'll want to leave this active for improved social media sharing.
Fallback image - Click Choose file or drag and drop an image onto this field to set the fallback image; this is the image that will be used in social media previews if no other is available e.g. from the shared post. If left blank, the site logo will be used as a fallback by default.
Use the page title in metatags - If this option is enabled then the og:title and twitter:title metatags will use the page title as their value, rather than the post title, tag or author name.
Facebook App ID - If you use a Facebook app integration, enter its App ID here. An App ID is not required for Publii to generate the other Open Graph tags. If needed, follow Facebook's guide to register an app.

Twitter Cards

Twitter Cards are very similar to Open Graph Tags in that they customize how your links will look when shared, but they are intended for X (formerly Twitter). Publii still labels these settings Twitter Cards. The options in this section are:

Generate Twitter Cards - Enables or disables Twitter Cards for your site.
Twitter Username - Enter your Twitter Username in this section; it's required when generating the cards.
Card Types - You can choose between a standard card or one with a large image; both function exactly the same mechanically.

Note: Open Graph and Twitter Card tags are not generated when Use relative URLs is enabled in Server Settings.

Privacy Settings

In this section of the guide we will cover the options available in the Privacy Settings section only; a full step-by-step guide to setting up the cookie banner and adding consent options for your site visitors is covered in a separate section of this guide; Publii GDPR Cookie Banner Configuration.

The Privacy Settings section controls the cookie banner and consent options for embedded content. Configure these to match the cookies and services your website actually uses. Enabling the banner alone does not connect every third-party script to a consent group; scripts must be configured to respect visitors' choices.

You can read more in our guide to making your website GDPR-compliant. For setup instructions, see GDPR Cookie Banner Configuration.

The options available in this section are:

Embed Video

Enable Privacy-Enhanced mode for YouTube videos - When this option is enabled, YouTube videos that are embedded in your post content will not be used by YouTube to customize your visitors' YouTube preferences such as recommended videos, nor will any personalized ads be shown.
Enable 'Do Not Track' mode for Vimeo videos - Adds Vimeo's Do Not Track parameter to embedded videos to limit tracking. Vimeo may still use essential cookies needed for the player to work securely.

Cookie Banner

Cookie banner - When enabled, the cookie banner will appear on your site.

Once the banner is enabled, the following additional options will appear to allow you to configure the popup:

Basic

Banner Title - Set the title that will appear at the top of the cookie banner.
Banner Message - Provide a description; this section should explain the type of cookies your website uses so that visitors can make an informed decision about consent.
Show Privacy Policy Link - When enabled, the cookie banner will include a link to your privacy policy page, informing visitors how their data will be used.
Privacy Policy Link label - Set the text that should be used for the Privacy Policy link in this field.
Privacy Policy Link Source - Sets whether the privacy policy link points to an internal or external URL.
Select Page - Only available if Privacy Policy Link Source is set to Internal. Choose a published page or post from the list, or type its title to filter the results. You can create a dedicated privacy policy using Pages, so it does not appear in your post listings.
Enter External URL - Only available if the Privacy Policy Link Source option is set to External. Enter the URL for your privacy policy into this field.
Save button label - Sets the text for the banner button that accepts all configured cookie groups. The default label is Accept all.
Show Reject Button - If enabled, a button allowing visitors to reject the optional cookie groups managed by the banner will be shown.
Reject Button Label - Sets the text to be displayed on the reject button if it is enabled.
Open Banner by - Defines the type of trigger to open the cookie banner; this should be left as the default Badge for most users, but advanced users can define a Custom link (for example, to include this in a Privacy Policy article), or Badge & custom link to use both.
Badge label - Sets the title text of the badge, used for the badge icon's accessible label. Visitors can click the badge to reopen their cookie settings.
Anchor link - Only available if the previous option is set to Custom link or Badge & custom link. Defines the link for the cookie settings.
Banner Position - Sets where on the page the cookie banner should display; can be set to Left, Right, Center, or Bar, which displays the banner as a bar along the bottom of the full-width of the screen.

Advanced

While the basic section covers the settings for the standard cookie banner, the advanced selection provides multiple options for fine-tuning the cookie banner, allowing visitors to manage which cookie types they wish to consent to. The options available in this section are:

Enable Advanced Cookies Configuration - Enabling this option adds the granular consent pop-up to the cookie banner, allowing visitors to specify which cookie groups they consent to receiving.
Advanced configuration link label - Sets the text for the link to the pop-up where visitors can manage their cookie preferences.
Pop-Up Title - Sets the title that appears at the top of the pop-up window.
Pop-Up Message - Add a message here to provide details regarding the available cookies and how visitors may give consent. Text entered here will appear directly under the title in the pop-up window.
Accept Button Label - Sets the text that will appear in the accept button in the pop-up; when visitors click on this button, it accepts all cookie groups managed by the banner.
Reject Button Label - Sets the text that will appear in the reject button in the pop-up. When visitors click on this button, it rejects the optional cookie groups managed by the banner.
Save Button Label - Sets the text for the save button in the pop-up. When visitors click on this button, it accepts only the selected cookie groups rather than accepting/rejecting all.
Privacy Policy Link - When enabled, a link to your site's privacy policy will be included in the pop-up. Note that if the 'Show privacy policy link' option in the basic settings is disabled, then this option will also be automatically disabled.
Enable Debug Mode - When enabled, the developer console will return a set of messages regarding the work of the banner or user consents.
Settings Version - Increasing this version number tells the visitor's browser that consent for new cookies is required; this will show the cookie banner once again. This can be useful when, for example, a new feature has been added to your site that uses a new type of cookie, and visitors need to consent to these new cookies.
Store User's Consent Settings For X Days - The number in this option sets the number of days for which the visitor's consent settings should be stored in their browser. After this time expires, they will need to re-consent via the cookie banner. Setting this option to 0 will remove any time limit.
Cookie groups - This section allows you to create and manage cookie groups that you can add your website's scripts to, which will then appear as tickboxes for visitors to select in the cookie pop-up. You may set:
- Group name, which is how the tickbox will be labeled in the cookie pop-up.
- Group ID, which is used to associate scripts with the group, as described in the cookie banner configuration guide.
- Group description, which explains what the group is used for.
More information on setting up your cookie banner can be found in the GDPR Cookie Banner Configuration article of this guide.

Google Consent Mode v2

This section connects the choices made in Publii's cookie banner to Google Consent Mode v2. It is useful when your website uses services such as Google Analytics or Google Ads and your Google tags are configured to receive consent signals. See Google's consent mode overview for how those signals affect tag behaviour.

Activation

To enable Google Consent Mode v2 support, you must activate this option within the Privacy Settings. Additional settings related to defining the default consent state and how user-expressed consents for different cookie groups influence the consents within Google Consent Mode v2 will become available upon activation.

Default State

The "Default state" option sets the baseline consent state transmitted in the gtag('consent', 'default', ...) call. Here, you decide which consents are always granted by default and which require explicit user approval.

Following this, under the "Default state" option, you can specify which consents are granted upon acceptance of each cookie group. This involves selecting a predefined cookie group and marking the permissions granted upon acceptance of that group.

For instance, if the analytics cookie group is selected with analytics_storage and ad_storage options, upon acceptance, a signal is sent as follows:

gtag('consent', 'update', {
    'analytics_storage': 'granted',
    'ad_storage': 'granted'
});

Subsequently, on page refresh or the next visit, the analytics_storage and ad_storage options will be marked as granted in gtag('consent', 'default', ...) by default, regardless of the "Default state" settings, until consent is withdrawn for the analytics cookie group.

Revoking Consent

When consent is withdrawn for a cookie group, Publii reloads the page rather than sending an update with denied values. It then calculates the default consent state again from the saved choices and your configured defaults. A permission remains granted if you granted it in the default state or another accepted group also grants it.

A denied consent signal does not necessarily stop all requests from Google tags; their behaviour also depends on how those tags are installed and configured.

It's important to understand that if a permission is not marked for a cookie group, it does not imply that a denied signal will be sent upon gtag('consent', 'update', ...) calls. Only consents that are explicitly granted are transmitted. Therefore, in the example above, only two consents with granted values are sent, not a complete set of seven consents with granted/denied values. Essentially, consenting to a cookie group overwrites the consent state to granted for the permissions marked within that group.

Embed Content Consents

This section is dedicated to adding rules to allow visitors to consent to third-party cookies from embedded content providers, such as YouTube or Vimeo. Instead of displaying embedded content, such as a YouTube video, a placeholder will be displayed in its place with a message and a button confirming that you consent to a third-party cookie. The options in this section are:

Add Rule - Clicking this button will open additional options where you can specify the URLs of the embedded content that requires cookie consent.
URL Contains - Enter the URL for the embedded content that requires cookie consent into this field e.g. if you use embedded YouTube videos, you can add youtube.com to this field.
Cookies Group - Sets which cookie group the visitor must consent to in order to view the embedded content. For that, select one of the available cookie groups previously created in the Cookie groups section.
Button Label - Sets the text for the accept button that will appear with the placeholder text should the visitor try to view embedded content without first consenting to the required cookies.
Consent Text - Text entered in this section will be displayed over the embedded content when a visitor has not consented to the appropriate cookies; it may be used to inform them of their requirement to consent before viewing the content.

Note: Embed consent rules require the cookie banner, advanced cookie configuration and support in your theme. Match the actual embed URL; YouTube privacy-enhanced embeds use youtube-nocookie.com.

Website Speed

These options help reduce file sizes and control how browsers load your website's assets. The options here are:

Enable HTML Compression - Enabling this option will compress the HTML code used for your site; for the most part you'll be able to leave this enabled and reap the benefits, but if advanced users want to disable it, they can.
Enable CSS Compression - The same as above, but this time compressing the CSS code rather than the HTML. Leave this enabled if you're unsure, as it'll give a little boost to your load times.
Remove HTML Comments - If enabled, comments in HTML (which are not displayed on a live site, but are used to highlight or explain things to people reading the source code) will be removed during the compression process.
Enable Media Lazy Load - Adds native lazy-loading attributes to media in your content. Supporting browsers can defer loading off-screen images and iframes; behaviour for other media depends on browser support.
Enable Responsive Images - If enabled, Publii will deliver different sized images at different screen resolutions depending on breakpoints defined in the theme's config.json file.
Version parameter - Adds a version parameter to CSS and JavaScript URLs so browsers can load updated files instead of cached versions. If a shared stylesheet or script changes, the HTML pages that reference its new URL may also need to be uploaded during sync.
Responsive Images Quality - Sets the compression quality of generated responsive images, from 1 to 100. Lower values generally produce smaller files with more visible compression. The default is 60%. This controls compression quality, not image dimensions, and is disabled when lossless WebP or AVIF compression is selected.

Image conversion

When Enable Responsive Images is active, you can choose the format of generated thumbnails:

No conversion - Keeps the original image format for generated thumbnails.
WebP - Converts JPG, JPEG and PNG thumbnails to WebP. Existing AVIF images keep their format. You can enable lossless compression or adjust Responsive Images Alpha Quality to control the quality of transparency in lossy WebP images.
AVIF - Converts JPG, JPEG, PNG and static WebP thumbnails to AVIF. You can enable lossless compression and choose Fast, Balanced or High compression effort. Higher effort takes longer and may produce smaller files at the same quality.

The original image files remain unchanged. After changing the conversion format, use Tools > Regenerate thumbnails to rebuild your thumbnails. AVIF encoding can take longer and does not always produce smaller files.

Responsive image settings in Publii with AVIF conversion selected, quality set to 60 percent and balanced compression effort. — Choose the format, quality and compression settings for generated image thumbnails.

RSS/JSON Feed

RSS and JSON Feeds are a way for your content to be syndicated and shared far beyond your site, encouraging new users to visit. For many people web feeds like this are an important way of staying on top of new content, with RSS and JSON offering different feed formats. The options in this section are:

Enable RSS feed - When turned on, an RSS feed will be generated for your site.
Enable JSON feed - When enabled, a JSON feed will be generated for your site.
Feed title - Choose whether to use the website name or a custom feed title. Selecting a custom title reveals a field where you can enter it.
Show full text - If this option is enabled then your website articles sent via the feed will include the full text, so users won't be required to visit your site for the complete article.
Post update date set as - When RSS is enabled, choose whether the post creation date or modification date is used for the update date in RSS feed entries.
Show only featured posts - When this option is enabled, the feeds will include only posts marked as featured.
Exclude featured posts - When this option is enabled, the feeds will exclude posts marked as featured. This option is available when Show only featured posts is disabled.
Number of posts in feed - Set how many articles people can access from the webfeed at once; default is set to 10.
Show featured image - When this option is enabled the Featured Image for each shared post will be included in the feed.

Note: RSS and JSON feeds are unavailable when Use relative URLs is enabled in Server Settings.

Posts Listing

The options in this section give you finer control over post ordering in your website's listings. The available options are:

Posts Order By - Set how the posts on the homepage are ordered; choose from Post Creation Date, Post Title, Post Modification Date, or Post ID.
Posts Ordering - Sets whether the posts follow ascending or descending order.
Featured Posts Order By - Sets the ordering style of featured posts on the homepage; the same options are available as with the standard post ordering.
Featured Posts Ordering - Sets the ordering of featured posts to ascending or descending.
Hidden Posts Order By - Sets the ordering style of hidden posts in post listings.
Hidden Posts Ordering - Sets the ordering of hidden posts to ascending or descending.
Related Posts Selection Mechanism - Sets how Publii should find related posts:
- Use Only Titles will look for similarities in other posts' titles to the current post.
- Use Only Tags will look for similarities in the tags used in other posts to the current post.
- Use Titles and Tags will combine both methods.
Related Posts Ordering - Sets the ordering of related posts to ascending or descending by ID, or can be set to Random.
Related Posts Options - When enabled, related posts will be taken from all tags. When disabled, related posts will only be generated from the same tags as the current post.

How featured, hidden and related posts appear depends on your theme. With random related-post ordering, the selection can change when the site is generated, so a sync may update more post pages than the one you edited.

Editors

This section contains options for the WYSIWYG and HTML source code editors.

WYSIWYG editor - If the content includes elements that are not part of standard HTML, the editor might remove them when you save the post. This option allows you to specify which non-standard elements should be kept. The editor validates content against its configured HTML rules.
For example: adding v-select[*], v-dropdown[*] will extend the list of allowed tags with custom v-select and v-dropdown tags with any attributes.
Remember!
1. First, add your custom elements in the initial window labeled 'Additional valid elements in the WYSIWYG editor' using wildcard selectors like v-select[*], v-dropdown[*].
2. Then, list only the custom element names (e.g., v-select, v-dropdown) in the section called 'Custom Elements available in the WYSIWYG Editor.' Both settings are needed to allow the custom elements and their attributes.
Code editor (CodeMirror) - disable or enable auto-indent and set the indent size for the CodeMirror HTML source code editor.

After making changes, click Save settings. Preview your website to check the result, then sync it when you are ready to publish the changes.