Should We Retain Both Sections When All Projects and Website Projects Show the Same Work?

When All Projects and Website Projects display the same work, first confirm whether the business needs two different browsing tasks. If All Projects actually includes websites, product interfaces, and branding, while Website Projects filters only websites, both can remain. If current and foreseeable work consists only of websites, reassess the need for two lists with the same purpose.

Different titles alone do not establish different section roles. Compare body introductions, project sets, filtering rules, and actual destination links before deciding to retain two scopes, clarify one entry point, or have implementers arrange canonical URLs. Make the business decision before adjusting technical signals, so changing titles does not leave the same problem in place.

Use Actual Scope Instead of Section Names

List the work currently shown in both sections item by item, recording work type, publication state, and detail URL. Identical covers and ordering do not necessarily mean complete duplication. However, if every destination is identical and introductions identify no different task, readers have little reason to enter the other list again.

Include pagination and filters in comparisons. The first screen may feature the same priority projects while later lists differ. Conversely, different first screens may only reflect ordering, with the same set appearing after paging. Checks must match the scope promised by the section, rather than examining only a few top images.

Ask about real future content plans too. Planned UI or branding additions can explain reserving an All Projects entry point, provided actual materials and publication conditions exist. Do not insert demonstration templates or unconfirmed commissions as real client projects merely to prove the sections differ.

The JVDS audit on October 2, 2026 compared the bodies, images, and destination-link sets of All Projects and Website Projects, recorded overlapping scope, and recommended clarifying roles or consolidating the canonical entry point. That record describes that day's finding. It does not show that all pages have now been adjusted or prove that search engines imposed a penalty. See How to Design Corporate Website Case Studies That Sell for related checks.

Assess Whether the Lists Support Different Choices

Write one task sentence for each section: 'Help visitors understand the team's published work across different types' and 'Help people preparing a business website compare website structures and delivery.' Then check whether list descriptions, category filters, and related entry points actually support those tasks. Task differences should be observable in the content.

If All Projects still contains only websites, state the current scope honestly rather than suggesting coverage of many business areas. Retaining a reserved section depends on whether navigation adds unnecessary choices and whether a definite owner exists for future maintenance. Future business possibilities should not be presented as capabilities already demonstrated.

Suppose a design team currently publishes website and logo work. All Projects can provide entry points for both types and selected projects, while the website section explains page structures, languages, and responsive applications. If both simply copy the same cards, entering the second section gives users no new basis for selection.

The simplest assessment is to ask visitors what different decision they can make after entering the second list. If the answer is only 'Look at the same projects again,' continue organizing scope. Section count does not represent portfolio depth, and an extra list is unnecessary merely to create an impression of scale.

When Retaining Both Sections, Put Differences Into Actual Rules

If retaining them separately, encode overall and subset scopes in real content rules. Each project needs a clear type, consistent publication status, and source boundaries. The overall section can cover confirmed different types, while the website section includes content suited to website tasks. Rules must be executable during administration, rather than relying on editors' intuition each time they choose images.

Section introductions should also differ. All Projects explains selecting types and viewing published outcomes; Website Projects explains attention to pages, content, and usage tasks. Do not replace 'All' with 'Website' and copy the same promotional paragraph. Introductions help readers understand the current collection, rather than increasing keyword repetitions.

Related recommendations and inquiry entry points can follow tasks. Website readers may want to understand redesign or development scope further; branding readers may need identity applications. Without supporting evidence, provide a clear service direction rather than adding unknown client achievements to every project.

Prevent renewed overlap when types change. For new work, check which lists show it, why it appears, and where it links. The overall section can guide type selection while subsections support deeper browsing. Once these roles are established, first-screen layout and recommendation order have a basis.

Assess One Entry Point When Scopes Really Match

If both lists consistently serve the same task, business and maintenance staff can confirm which to retain as the main entry point. Consider existing navigation, external citations, analytics objects, and long-term maintenance, rather than only which URL is shorter. Collect entry-point information first when materials are missing, avoiding immediate deletion of a heavily used path.

Consolidating entry points involves pages and technical settings. Implementers should arrange how old entry points reach relevant content and check consistency of internal links and sitemaps. Google's canonical-URL guidance requires different canonicalization methods to avoid contradiction, and internal links to consistently point to the preferred version.Official Canonical URL Guidance

Business owners need not fill in all code themselves, but should identify the page readers should ultimately enter. Canonical declarations, navigation, sitemaps, and old-URL handling should serve the same decision. Adjusting one tag while menus continue randomly pointing to both scopes increases explanation and maintenance burdens. See How to Use Canonical Tags Correctly for related checks.

Check Chinese and English tasks and content separately. Consolidating Chinese lists does not justify pointing English entry points to Chinese pages in place of complete English access. Language-version relationships and duplicate scopes in one language are different issues, requiring treatment according to actual content. Confirm that previously working language-browsing tasks still work after changes.

Create a Section-Scope Decision Record

Record the two existing sections, current work sets, target reader tasks, reasons for retaining or consolidating, actual rules, and relevant URLs. If assigning different roles, include entry conditions for each work type. If consolidating, include the retained entry point and subsequent handling of old paths. The record helps apply the same decision to later additions.

Identify evidence gaps too. Without search data or external-link sources, do not use 'Certainly nobody uses it' as grounds for deletion. Without other work types, do not present 'We may have them later' as a current scope difference. When information is incomplete, complete the inventory before making limited adjustments.

Verify file updates and section tasks separately. Changed titles prove wording changes; genuinely different filtered sets prove scope rules work. When consolidating entry points, check original URLs, navigation clicks, and language paths instead of only the target page's first screen.

The checklist can also record a future review condition, such as reconsidering All Projects organization when a second type of published work is added. Reserved plans then have a clear trigger instead of leaving a hollow duplicate entry point permanently on the site.

Complete Acceptance Through Real Visitor Browsing Tasks

Enter the portfolio from the homepage or a service page, select a type, open details, and return to continue comparing. The check should retain section scope, pagination position, and language. If returning goes to an unrelated overall list or removes subtype information, complete the whole browsing path.

Testers can use two clear scenarios: understanding the team's overall work and comparing website projects only. After completing each, explain whether two entry points reduce selection effort or make people repeat the same route. Record the work set and entry points observed, rather than treating personal aesthetic preferences as scope acceptance.

Completion can mean two sections have observable type and task differences, or one long-term primary entry point has been established. Introductions are accurate, links work, and publication and language scopes match. Observe search effects separately later; section organization alone does not establish improved rankings or inquiries.

Use the decision record to check scope as work is added. A clear list system makes maintenance easier for the business and comparison of real outcomes easier for visitors, rather than growing section names while continually showing the same images.

Frequently Asked Questions

Can Two Lists Count as Different Sections if Only Their Introductions Change?

That depends on whether actual tasks and work scopes differ. Wording helps explain roles but cannot replace content rules. Identical sets and paths still need reassessment.

Should We Immediately Delete All Projects if It Currently Contains Only Websites?

Avoid mechanical treatment. Check existing entry points and real content plans first, confirm whether retention helps readers, then have implementers arrange appropriate changes.

Can a Project Appear in Both Lists?

Yes. A subset normally belongs within an overall scope. The question is whether each page has an independent task, rather than requiring every cover to be mutually exclusive.

Do Duplicate Lists Mean a Search Penalty Has Occurred?

This finding alone cannot establish a penalty. This article concerns content roles and URL consistency. How search systems actually handle them requires corresponding platform evidence.

Can Template Demonstrations Supplement a Portfolio Without Other Work Types?

Demonstrations should clearly identify themselves and have a separate scope. They cannot serve as proof of client commissions. Section introductions must accurately describe the source of displayed work.