Naming Rules

Overview

The Naming rules section allows you to define how duplicated posts, pages, and custom post types are named.

Naming rules are profile-based, which means each duplication profile can use its own naming pattern. This helps keep duplicated content organized and easy to identify.

How naming rules work

When duplicating content, Duplicate Post RB builds the new title using three parts:

Prefix
Original name
Suffix

You can leave any of these fields empty or combine them as needed. A live preview shows how the final title will look before duplication.

Available shortcodes

Duplicate Post RB supports dynamic shortcodes that can be used in prefixes and suffixes.

`[Counter]`

Automatically increments with each duplication.

Useful for creating sequential copies such as:

Page (1)
Page (2)
Page (3)

`[CurrentDate]`

Inserts the current date into the duplicated title.

The date format can be customized in the profile settings.

`[CurrentTime]`

Inserts the current time into the duplicated title.

The time format can also be customized to match your preferences.

Preview field

The Preview field shows how the duplicated item will be named using the current configuration.

This helps prevent mistakes and makes it easier to adjust naming rules before duplicating content.

Counter start value

The Counter start value defines the initial number used by the [Counter] shortcode.

This is useful when:

continuing an existing sequence
avoiding conflicts with already duplicated content
organizing large sets of copied items

Date and time formats

You can customize how dates and times appear in duplicated titles.

Time format

Uses standard PHP date format characters (for example: h:i:s).

Date format

Also uses PHP date format characters (for example: d/m/Y).

This allows full control over localization and formatting.

Profile-based behavior

Naming rules are saved per duplication profile.

This allows you to:

use simple names for quick drafts
add counters for bulk duplication
include dates or times for versioned content
keep different naming strategies for different workflows

Best practices

Use counters for bulk duplication
Include dates for versioned or temporary content
Keep naming rules simple and readable
Create separate profiles for different naming strategies

Documentation