Attribution Settings: Attribution Footer and Discovery Listing #

Attribution Settings control two project-level switches:

• Attribution Footer: adds a subtle "Generated with PublizAI" line to published posts.
• Discovery Listing: allows your project website to appear on the public /discover page.

Recommended default #

For most businesses, keep both settings ON. This improves visibility, supports social proof, and keeps your project connected to PublizAI growth analytics.

Where to configure it #

1. Open /workspace/settings/attribution.
2. In Project Controls, choose the project you want to configure.
3. Toggle Attribution Footer and Discovery Listing for that project.
4. Click Save Attribution Settings.

What each setting changes #

Attribution Footer #

• Appends a lightweight attribution line at publish time.
• Keeps content ownership with your brand while indicating publishing infrastructure.
• Contributes to attribution click tracking and ecosystem discoverability.

Discovery Listing #

• Controls whether that project is eligible to appear on the discovery page.
• Eligibility is strongest after at least one successful published post.
• Lets potential customers and partners discover your site as an active PublizAI user.

Verification checklist after saving #

1. Publish one post from the selected project.
2. Open the live post and confirm attribution footer appears as expected.
3. Open /discover and confirm listing after sync.
4. Recheck project toggles if the site is not visible yet.

Benefits of keeping Attribution Settings ON #

• Increases external visibility from PublizAI channels.
• Creates additional trust through transparent publishing attribution.
• Strengthens discovery network effects across active customers.
• Improves internal measurement for attribution and growth reporting.

When turning a setting OFF is reasonable #

• Strict white-label contract requirements.
• Temporary brand/legal review windows.
• Controlled campaign testing where attribution needs isolation.

Best-practice policy #

Keep both settings ON by default and only disable per project with a documented reason and review date.