Several Matomo requests do not necessarily mean duplicate page views. A page view, an event and two intentionally separate site IDs can have different purposes. Compare request type and destination before removing an integration.
Use non-personal test data under the intended consent conditions. Record a direct entry and count page-view requests targeting the same site ID.
Locate the generating components
Inspect directly embedded code, Tag Manager, plugins and custom routing listeners. A fictional duplicate pattern would send trackPageView on initial load and again through an additional page listener.
Resolve overlapping responsibility at its source. Remove the extra trigger in code or Tag Manager. Toggle suspected sources only on a controlled test environment so that unrelated measurement does not disappear.
After the fix, test a full load, internal navigation and any client-side route transition. Inspect destination and request type for each. A second Matomo property may be intentional; document it rather than assuming it is wrong.
Also verify that requests remain gated as required. Test rejection and acceptance in separate fresh sessions. Record the affected historical period separately: a code correction does not automatically clean previously collected data.