---
title: "FAQs"
url: https://docs.coolplugins.net/doc/toolkit-for-polylang-faqs/
date: 2026-10-15
modified: 2026-10-15
lang: en
author: "Satinder Singh"
description: "Plugin Compatibility Q1. Does Toolkit for Polylang require Polylang? Ans: Yes. Polylang must be installed and activated because Toolkit for Polylang works as an addon for Polylang multilingual websites. Q2...."
categories:
  - "Toolkit for Polylang – Translation Inspector & Duplicate Content"
word_count: 665
---

# FAQs

## Plugin Compatibility

**Q1. Does Toolkit for Polylang require Polylang?**
**Ans:** Yes. **Polylang **must be installed and activated because Toolkit for Polylang works as an addon for Polylang multilingual websites.

**Q2. Does Toolkit for Polylang replace Polylang?**
**Ans:** No. Polylang continues to manage your website languages and translation relationships. Toolkit for Polylang adds tools to help you inspect multilingual issues and manage duplicate content.

**Q3. Which editors are supported by Duplicate Content?**
**Ans:** Duplicate Content works with posts and pages created using the **Classic Editor** and **Gutenberg Block Editor**.
Elementor pages are not duplicated by Toolkit for Polylang because Elementor handles its own page duplication workflow.

**Q4. Does Translation Inspector support Elementor?**
**Ans:** Yes. Translation Inspector includes supported checks for Elementor multilingual setups, including templates, headers, footers, translated templates, and display conditions.

**Q5. Can I use AI translation with Toolkit for Polylang?**
**Ans:** Yes. You can use the optional **AI Translation for Polylang** addon to translate content with supported AI translation providers.
AI Translation is separate from the built-in Translation Inspector and Duplicate Content tools.

**Q6. Can I add a language switcher with Toolkit for Polylang?**
**Ans:** You can use the optional **Language Switcher for Polylang** addon with Toolkit for Polylang. It supports language switchers for **Gutenberg, Elementor, Divi**, and a **Floating Language Switcher**.

**Q7. Do I need to enable both Translation Inspector and Duplicate Content?**
**Ans:** No. You only need to keep **at least one built-in tool enabled**. You can use Translation Inspector, Duplicate Content, or both depending on your workflow.

## Common Issues & Solutions

**Q1. Why is the Scan Website button disabled?**
**Ans: **The **Scan Website** button may remain disabled if some content does not have a default language assigned.
Click **Set to default language**. Toolkit for Polylang will assign the default language to the affected content and then allow the scan to continue.

**Q2. How do I start a new website scan?**
**Ans:** From your WordPress website, navigate to **Languages > Toolkit for Polylang > Translation Inspector**, then click **Scan Website**. Once the scan is complete, the results will appear in the Translation Health Report.

**Q3. What should I fix first after running a scan?**
**Ans: **Start with findings marked **Critical**, followed by **Warnings**. Open each issue first to understand what was detected, which content or language is affected, and the suggested solution before making changes.

**Q4. How can I check whether an issue has been fixed?**
**Ans:** After fixing a detected issue, use the **individual rescan** option. This checks that specific finding again without requiring a complete website scan. You can also run a full scan after making changes across multiple areas of your site.

**Q5. What does Ignored mean in Translation Inspector?**
**Ans: **An **Ignored** issue is a finding you have intentionally chosen not to address. This can be useful for content that is intentionally the same across languages, such as product names, company names, or technical terms.

**Q6. Why is an issue still showing after I fixed it?**
**Ans:** Use the **Rescan issue** option after making the change. The previous scan result may continue to appear until that issue or the complete website is scanned again.

**Q7. Why is my translation coverage low?**
**Ans:** A low translation coverage percentage generally means that some supported content still does not have translations in one or more active languages. Open the **Coverage** or **Content** section to review the affected content.

**Q8. Why is Duplicate Content not appearing for my Elementor page?**
**Ans:** Toolkit for Polylang does not duplicate Elementor pages because Elementor handles its own duplication workflow. Duplicate Content is intended for content created using the **Classic Editor** or **Gutenberg**.

**Q9. Does Duplicate Content automatically translate the copied page?**
**Ans:** No. Duplicate Content copies the existing source content into the new Polylang language version. You can then translate the content manually or use the optional **AI Translation for Polylang** addon.

**Q10. Why are Elementor issues not appearing in Translation Inspector?**
**Ans:** Make sure Elementor is active and that your website contains supported Elementor templates or multilingual configurations that Translation Inspector can review. After making changes, run another website scan to refresh the results.