Introduction
If you're managing multiple domains under one Newsifier account — especially domains in different languages — resource mapping helps you ensure that categories, tags, and authors are matched correctly across those sites. For example, the tag Politics
in English can be mapped to its equivalent Politiek
in Dutch or Política
in Spanish, so articles appear under the correct translated tag or category on each domain.
This article explains how to use the Resource Mapping feature
What is Resource Mapping?
Resource mapping allows you to manage how tags, categories, and authors are linked between domains when publishing the same article to multiple websites.
This is especially useful for:
Multi-language setups, where tag/category slugs and names differ between languages
Independent domain structures, where naming conventions are not consistent
🌍 Multilingual Example
Let’s say your main site is in Dutch, and you also publish to an English version of your website.
On your Dutch site, you have a tag called
politiek
On your English site, you want that same tag to appear as
politics
Using Resource Mapping, you link:
politiek
(Dutch domain) →politics
(English domain)
Now, any article tagged with politiek
on the Dutch domain will automatically use the politics
tag when shared to the English domain.
Who Is This Feature For?
This feature is for publishers who use Newsifier’s multi-domain publishing functionality — where an article can be shared with one or more connected websites.
It is especially useful for:
Publishers with multilingual websites, where each domain uses different languages and you want tags, categories, and authors to be matched correctly between translations.
Organizations managing multiple regional or brand domains that have different taxonomies or naming conventions.
By mapping resources across domains, you ensure that shared articles are correctly categorized and attributed — regardless of language or site structure.
Where to Find Resource Mapping
To access the Resource Mapping screen:
You will see a table showing all your connected domains.
The first column (fixed and not scrollable) represents the domain you're currently managing.
The following columns represent the domains you are mapping resources to.
How to Use the Mapping Table
The table has four tabs:
Tags
Categories
Authors
Articles (mainly informational for reference)
Available Filters:
Connected domains: Select specific domains to view/edit mappings.
Only show unmapped resources: Helps you quickly find what still needs to be mapped.
Search: Search by tag, category, or author slug.
⚠️ The mapping table uses slugs, not the full names. So while you can search by name, the actual values shown are slugs.
How Mapping Works
Here’s how you can link resources between domains:
1. 🏷️ Tags
Example:
You publish an article on Domain A with the tag Sports
, but on Domain B, the equivalent tag is called Athletics
.
In the Tags tab of Resource Mapping, you link:
Sports
(Domain A) →Athletics
(Domain B)
Now, whenever an article with the tag Sports
is sent from Domain A to Domain B, it will appear under Athletics
.
🔹 If no tag is mapped, the article will be sent without any tag.
2. 🗂️ Categories
Each article must have a valid category to be published.
Example:
Let’s say you have a category called politics
on Domain A, and you want the article to be categorized under Local-news
on Domain B.
In the Categories tab, link:
politics
(Domain A) →Local-news
(Domain B)
✅ This ensures the article is published correctly. If a category is not mapped, publishing on the destination domain may fail if the sending type with auto-publish.
3. ✍️ Authors
You can also map authors between domains to ensure the correct author appears on the receiving site.
Example:
Anna Johnson
is the author on Domain A. You want the article to show as written by News Team
on Domain B.
In the Authors tab, link:
Anna Johnson
(Domain A) →News Team
(Domain B)
💡 If no author is mapped, a default author can be used — see below.
What Happens If a Tag or Category Isn’t Mapped?
To clarify how tags and categories behave when no mapping is specified:
✅ If the two domains are in the same language, and a tag or category with the same name already exists in the destination domain, the system will automatically use that existing tag or category. This helps avoid duplicates and ensures the article is still categorized correctly even without an explicit mapping.
If the tag or category doesn’t exist in the second domain, it will be automatically copied.
⚠️ If the domains are in different languages, and no mapping is provided in Resource Mapping, then the tag or category will not be transferred to the other domain. This prevents assigning untranslated or mismatched terms across multilingual sites.
Additionally, if no mapped category exists, the article will be sent as a draft on the destination domain , since every article requires a valid category to be published.
To ensure consistent behavior across your domains — especially in multilingual setups — we recommend always mapping key tags and categories explicitly.
Additional Options (Setup Required by Newsifier)
You can ask Newsifier support to enable the following settings to make cross-domain publishing faster and more efficient:
✅ Auto-select domains when sharing an article
By default, when you open the article publishing panel, no domains are pre-selected — you need to manually choose the domains you want to share the article with.
If you'd like to automatically pre-select all connected domains every time you create or edit an article, we can activate this setting for you.
🔹 This is useful if you frequently publish the same content across multiple sites and want to avoid selecting domains manually each time.
✅ Set a default status for shared articles (e.g., always Published or always Draft)
When you share an article to other domains, you can choose whether it should be published immediately or saved as a draft on those domains.
If you'd like this status to be pre-filled automatically every time, Newsifier can set a default sharing status for you:
Always publish shared articles by default
Always send them as drafts by default
💡 You can still change the status manually per article, but this saves time if you usually follow the same workflow.
✅ Assign a default author when no matching author is mapped
If an article is sent from Domain A to Domain B, and the original author doesn’t exist or isn’t mapped in Domain B, the system will leave the author field empty — which may cause issues or confusion on the receiving domain.
To avoid this, you can request Newsifier to assign a default author on the receiving domain when no mapped author is found.
For example:
If
John Smith
on Domain A is not mapped to any author in Domain B,The system will automatically assign the author
Editorial Team
on Domain B (or any author you specify as default).
Just let our support team know which author to use as the default per domain.📩 To activate any of these options, please contact our support team and let us know your preferences.
Summary
Resource mapping helps you:
Link and manage tags, categories, and authors between domains
Ensure smooth article sharing with correct metadata
Avoid manual duplication or publishing errors
If you have questions or would like help configuring your mappings, feel free to reach out to our support team.