WPIntell

Source evidence

Feedback 2

Content Importer for Notion · support · 2025-03-13T09:18:00+00:00

complaintsentiment
mediumseverity
0.88relevance
0replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

7 / 35 rows with source links

20.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

28 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
lilybennett unresolved
Subject: Feedback & Improvement Suggestion for the Plugin Hi Patrick, First of all, I want to thank you for the great work on the plugin. It’s really helping me push content quickly from Notion to WordPress, and I appreciate its efficiency. However, I’ve noticed a few limitations that significantly affect its potential, and I wanted to share my thoughts to help improve the plugin. Key Issue: Shortcode-Based Rendering Right now, the plugin relies on shortcodes to display content, but this approach comes with several drawbacks: 1️⃣ SEO Tools Don’t Work Properly – Since the content is not directly in the WordPress editor, SEO plugins (like RankMath or Yoast) can’t analyze it, making SEO optimization much harder. 2️⃣ Internal Linking & Automation Issues – Automatic internal linking tools (such as LinkJuicer) don’t work, which severely limits content efficiency and discoverability. 3️⃣ Editing Flexibility & WordPress Standards – Relying on shortcodes makes it harder to integrate with Gutenberg blocks , which are the standard for modern WordPress content editing. Suggested Improvement: Gutenberg Block Support To make the plugin truly powerful and seamless , it would be ideal if it allowed importing content directly into native WordPress blocks instead of relying on shortcodes. This would: ✔ Make SEO tools fully operational by having the content directly in the editor. ✔ Enable automatic internal linking with tools like LinkJuicer. ✔ Improve compatibility with other WordPress features and increase flexibility. My Current Workaround Since I still find the plugin very useful for pushing content, here’s how I work around the issue: I use the plugin to import and display content quickly . Once an article reaches maturity in my Notion database (i.e., when I consider it final and won’t revise it anymore), I manually convert it into a Gutenberg post by copy-pasting the content and removing the shortcode. I then delete the Notion version to keep my database clean. This method works, but it’s far from optimal , and I believe the plugin could be much more powerful with native block support. Would you consider adding an option for Gutenberg block integration in future updates? I think it would make a huge difference in usability and adoption. Again, I really appreciate the work you’ve done on this plugin, and I hope this feedback helps! Best regards, Lilly This topic was modified 1 year, 2 months ago by lilybennett .

Comments

0 shown

No comments were stored for this source.